From: Ben Nizette <bn@niasdigital.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: tickless and HZ=1000 throughput advantage?
Date: Sun, 20 Sep 2009 09:12:29 +1000 [thread overview]
Message-ID: <1253401950.7587.7.camel@ben-desktop> (raw)
In-Reply-To: <6278d2220909191050l19f2a446r5ccf1907fd963096@mail.gmail.com>
On Sat, 2009-09-19 at 18:50 +0100, Daniel J Blueman wrote:
> Agreed. Do you think there is still a small case for moving to HZ=1000
> (given it's effectively free) in situations like:
Sure HZ=1000 gives you more accurate sleeps, that's kind of the point,
but since when has it been "effectively free"?
http://lwn.net/Articles/331607/
--Ben.
next prev parent reply other threads:[~2009-09-19 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 14:47 tickless and HZ=1000 throughput advantage? Daniel J Blueman
2009-09-19 14:55 ` Arjan van de Ven
2009-09-19 17:50 ` Daniel J Blueman
2009-09-19 23:12 ` Ben Nizette [this message]
2009-09-20 7:34 ` Tim Blechmann
2009-09-20 7:40 ` Arjan van de Ven
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=1253401950.7587.7.camel@ben-desktop \
--to=bn@niasdigital.com \
--cc=arjan@infradead.org \
--cc=daniel.blueman@gmail.com \
--cc=linux-kernel@vger.kernel.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