From: Gerd von Egidy <lists@egidy.de>
To: kvm-devel@lists.sourceforge.net
Cc: Charles Duffy <Charles_Duffy@messageone.com>
Subject: Re: disappointing speed with virtio_blk
Date: Sun, 13 Apr 2008 23:55:39 +0200 [thread overview]
Message-ID: <200804132355.41342.lists@egidy.de> (raw)
In-Reply-To: <ftttii$us7$1@ger.gmane.org>
Hi Charles,
thanks for the quick reply.
> My understanding is that virtio is very latency-sensitive. Do you know
> whether your system is configured for high-resolution timer support, and
> (more to the point) which clock source KVM is using on your host?
On the host:
> grep "Clock Event Device" /proc/timer_list
Clock Event Device: hpet
Clock Event Device: lapic
Clock Event Device: lapic
Within the vm:
> grep "Clock Event Device" /proc/timer_list
Clock Event Device: pit
Clock Event Device: lapic
Host and vm use the same kernel, CONFIG_HIGH_RES_TIMERS=y
How do I find out which clock source KVM is using?
Kind regards,
Gerd
--
Address (better: trap) for people I really don't want to get mail from:
james@cactusamerica.com
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-13 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 21:04 disappointing speed with virtio_blk Gerd von Egidy
2008-04-13 21:22 ` Charles Duffy
2008-04-13 21:55 ` Gerd von Egidy [this message]
2008-04-14 0:29 ` Marcelo Tosatti
2008-04-16 23:05 ` Gerd von Egidy
2008-04-16 23:40 ` Marcelo Tosatti
2008-04-18 21:27 ` Gerd von Egidy
2008-04-18 21:49 ` Marcelo Tosatti
2008-04-18 22:32 ` Gerd von Egidy
2008-04-14 1:41 ` Anthony Liguori
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=200804132355.41342.lists@egidy.de \
--to=lists@egidy.de \
--cc=Charles_Duffy@messageone.com \
--cc=kvm-devel@lists.sourceforge.net \
/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