From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Matthew Kent <mkent-rTVjrLRGJfNWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Dan Kenigsberg <dank-atKUWr5tajBWk0Htik3J/w@public.gmane.org>,
qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH/RFC 4/4] Add support for dynamic ticks.
Date: Sun, 19 Aug 2007 11:08:42 +0300 [thread overview]
Message-ID: <46C7FA8A.2090900@qumranet.com> (raw)
In-Reply-To: <42755.207.81.93.54.1187334969.squirrel-N19E6/cp6YFSV923RJcDwA@public.gmane.org>
Matthew Kent wrote:
>> If DYNAMIC_TICKS is defined qemu does not attepmt to generate SIGALRM at a
>> constant rate. Rather, the system timer is set to generate SIGALRM only
>> when it is needed. DYNAMIC_TICKS reduces the number of SIGALRMs sent to
>> idle dynamic-ticked guests.
>> Original patch from Dan Kenigsberg <dank-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
>>
>> Signed-off-by: Luca Tettamanti <kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>>
>
> Wow, this patch sure made a difference for some timings I've been doing
> with kvm-35 and hackbench. All tests using 2.6.23-rc3+hrtimers patch for
> x86_64/i386 tickless and a quad core intel:
>
> [mkent@localhost ~]$ time ./hackbench 50
> x86_64 host : real 0m10.845s
> x86_64 host, bound to 1 cpu : real 0m21.884s
> i386 guest+unix clock : real 0m49.206s
> i386 guest+hpet clock : real 0m48.292s
> i386 guest+dynticks clock : real 0m28.835s
>
> Results are repeatable and verfied with a stopwatch because I didn't
> believe them at first :)
>
> Great stuff.
>
I'm not sure what these results mean...
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-19 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 20:41 [PATCH/RFC 0/4] Rework alarm timer infrastrucure Luca Tettamanti
[not found] ` <11872968773449-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-16 20:41 ` [PATCH/RFC 1/4] " Luca Tettamanti
[not found] ` <11872968771257-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-16 20:41 ` [PATCH/RFC 2/4] Add -clock option Luca Tettamanti
[not found] ` <11872968773155-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-16 20:41 ` [PATCH/RFC 3/4] Add support for HPET periodic timer Luca Tettamanti
[not found] ` <11872968773524-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-16 20:41 ` [PATCH/RFC 4/4] Add support for dynamic ticks Luca Tettamanti
[not found] ` <1187296877557-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-17 7:16 ` Matthew Kent
[not found] ` <42755.207.81.93.54.1187334969.squirrel-N19E6/cp6YFSV923RJcDwA@public.gmane.org>
2007-08-19 8:08 ` Avi Kivity [this message]
2007-08-17 12:44 ` [PATCH/RFC 0/4] Rework alarm timer infrastrucure Avi Kivity
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=46C7FA8A.2090900@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=dank-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mkent-rTVjrLRGJfNWk0Htik3J/w@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org \
/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