Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751963AbdLNL5A (ORCPT ); Thu, 14 Dec 2017 06:57:00 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56264 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751729AbdLNL47 (ORCPT ); Thu, 14 Dec 2017 06:56:59 -0500 Subject: Re: [PATCH RFC 0/7] kvm pvtimer To: Konrad Rzeszutek Wilk , Quan Xu Cc: Radim Krcmar , Yang Zhang , kvm , LKML , Ben Luo References: <1512722390-3654-1-git-send-email-quan.xu0@gmail.com> <20171208151014.GE12069@x230.dumpdata.com> <20171213162800.GS10097@char.us.oracle.com> From: Paolo Bonzini Message-ID: <78ebabd2-cc38-2694-b104-c5e0230aba15@redhat.com> Date: Thu, 14 Dec 2017 12:56:54 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171213162800.GS10097@char.us.oracle.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Thu, 14 Dec 2017 11:56:59 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 957 Lines: 26 On 13/12/2017 17:28, Konrad Rzeszutek Wilk wrote: > 1) VM idle path and network req/resp services: > > Does this go away if you don't hit the idle path? Meaning if you > loop without hitting HLT/MWAIT? I am assuming the issue you are facing > is the latency - that is first time the guest comes from HLT and > responds to the packet the latency is much higher than without? > > And the arming of the timer? > 2) process context switches. > > Is that related to the 1)? That is the 'schedule' call and the process > going to sleep waiting for an interrupt or timer? > > This all sounds like issues with low-CPU usage workloads where you > need low latency responses? Even high-CPU usage, as long as there is a small idle time. The cost of setting the TSC deadline timer twice is about 3000 cycles. However, I think Amazon's approach of not intercepting HLT/MWAIT/PAUSE can recover most of the performance and it's way less intrusive. Thanks, Paolo