linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dor Laor <dor.laor@gmail.com>
To: mingo@elte.hu, tglx@linutronix.de
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Performance overhead of get_cycles_sync
Date: Tue, 11 Dec 2007 15:11:39 +0200	[thread overview]
Message-ID: <475E8C8B.7070308@qumranet.com> (raw)

Hi Ingo, Thomas,

In the latest kernel (2.6.24-rc3) I noticed a drastic performance 
decrease for KVM networking.
The reason is many vmexit (exit reason is cpuid instruction) caused by 
calls to gettimeofday that uses tsc sourceclock.
read_tsc calls get_cycles_sync which might call cpuid in order to 
serialize the cpu.

Can you explain why the cpu needs to be serialized for every gettime call?
Do we need to be that accurate? (It will also slightly improve physical 
hosts).
I believe you have a reason and the answer is yes. In that case can you 
replace the serializing instruction
with an instruction that does not trigger vmexit? Maybe use 'ltr' for 
example?

Regards,
Dor.

             reply	other threads:[~2007-12-11 13:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 13:11 Dor Laor [this message]
2007-12-11 13:37 ` Performance overhead of get_cycles_sync Ingo Molnar
2007-12-11 14:14   ` Dor Laor
     [not found]   ` <475E9A92.4030001@qumranet.com>
2007-12-11 14:27     ` Ingo Molnar
2007-12-11 15:03       ` Dor Laor
2007-12-11 16:35       ` Arjan van de Ven
2007-12-11 17:03         ` Ingo Molnar
2007-12-11 17:23           ` Andi Kleen
2007-12-11 20:19             ` Ingo Molnar
2007-12-11 20:29               ` Ingo Molnar
2007-12-11 21:26       ` [kvm-devel] " Joerg Roedel
2007-12-11 14:27 ` Andi Kleen
2007-12-11 14:57   ` Dor Laor
2007-12-11 15:02     ` Andi Kleen

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=475E8C8B.7070308@qumranet.com \
    --to=dor.laor@gmail.com \
    --cc=dor.laor@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).