From: Andi Kleen <ak@suse.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Zachary Amsden <zach@vmware.com>, Andrew Morton <akpm@osdl.org>,
xen-devel@lists.xensource.com,
Christoph Hellwig <hch@infradead.org>, Jack Lo <jlo@vmware.com>,
Greg KH <greg@kroah.com>, Rusty Russell <rusty@rustcorp.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org, Linus Torvalds <torvalds@osdl.org>,
James.Bottomley@steeleye.com, pazke@donpac.ru
Subject: Re: A proposal - binary
Date: Sat, 5 Aug 2006 13:57:09 +0200 [thread overview]
Message-ID: <200608051357.09432.ak@suse.de> (raw)
In-Reply-To: <20060805104735.GS25692@stusta.de>
> Has anyone measured the performance impact of rutime CLOCK_TICK_RATE
> switching (since this will no longer allow some compile time
> optimizations in jiffies.h)?
SUSE shipped a kernel briefly that had runtime switchable jiffies
and there were some benchmarks done and they didn't show noticeable
slowdown.
But with hr timers it should be pretty much obsolete anyways.
-Andi
next prev parent reply other threads:[~2006-08-05 11:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44D1CC7D.4010600@vmware.com>
[not found] ` <20060803190605.GB14237@kroah.com>
[not found] ` <44D24DD8.1080006@vmware.com>
[not found] ` <20060803200136.GB28537@kroah.com>
[not found] ` <20060804183448.GE11244@sequoia.sous-sol.org>
[not found] ` <44D3B0F0.2010409@vmware.com>
2006-08-04 21:26 ` A proposal - binary Alan Cox
2006-08-05 1:14 ` James Bottomley
2006-08-05 5:37 ` Zachary Amsden
2006-08-05 10:42 ` Adrian Bunk
2006-08-05 11:50 ` Alan Cox
2006-08-04 22:01 ` Andi Kleen
2006-08-04 22:39 ` Zachary Amsden
2006-08-04 22:52 ` Andi Kleen
2006-08-04 22:43 ` David Lang
2006-08-05 10:47 ` Adrian Bunk
2006-08-05 11:57 ` Andi Kleen [this message]
2006-08-05 1:30 ` James Bottomley
2006-08-05 4:33 ` Zachary Amsden
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=200608051357.09432.ak@suse.de \
--to=ak@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=chrisw@sous-sol.org \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jlo@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pazke@donpac.ru \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=zach@vmware.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;
as well as URLs for NNTP newsgroup(s).