mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: yunhong jiang <yunhong.jiang@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Wanpeng Li" <kernellwp@gmail.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	"Wanpeng Li" <wanpeng.li@hotmail.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"David Matlack" <dmatlack@google.com>,
	"Christian Borntraeger" <borntraeger@de.ibm.com>,
	"Yang Zhang" <yang.zhang.wz@gmail.com>
Subject: Re: [PATCH v5] KVM: halt-polling: poll for the upcoming fire timers
Date: Thu, 26 May 2016 13:33:31 -0700	[thread overview]
Message-ID: <20160526133331.5aadf122@jnakajim-build> (raw)
In-Reply-To: <c66b94e0-45db-b8bd-1d63-c3d781afd5ce@redhat.com>

On Thu, 26 May 2016 12:26:27 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:

> 
> 
> On 25/05/2016 04:47, Wanpeng Li wrote:
> > From: Wanpeng Li <wanpeng.li@hotmail.com>
> > 
> > If an emulated lapic timer will fire soon(in the scope of 10us the
> > base of dynamic halt-polling, lower-end of message passing workload
> > latency TCP_RR's poll time < 10us) we can treat it as a short halt,
> > and poll to wait it fire, the fire callback apic_timer_fn() will set
> > KVM_REQ_PENDING_TIMER, and this flag will be check during busy poll.
> > This can avoid context switch overhead and the latency which we wake
> > up vCPU.
> 
> As discussed on IRC, I would like to understand why the adaptive

Glad to know the IRC channel. Is #kvm channel on freenode the IRC you are
talking about?

Thanks
--jyh

  parent reply	other threads:[~2016-05-26 20:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25  2:47 Wanpeng Li
2016-05-26 10:26 ` Paolo Bonzini
2016-05-26 10:30   ` Paolo Bonzini
2016-05-26 11:23     ` Wanpeng Li
2016-05-26 20:33   ` yunhong jiang [this message]
2016-05-27  9:49     ` Paolo Bonzini
2016-05-28  0:14       ` yunhong jiang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160526133331.5aadf122@jnakajim-build \
    --to=yunhong.jiang@linux.intel.com \
    --cc=borntraeger@de.ibm.com \
    --cc=dmatlack@google.com \
    --cc=kernellwp@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=wanpeng.li@hotmail.com \
    --cc=yang.zhang.wz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®