public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Blechmann <tim@klingt.org>
To: linux-kernel@vger.kernel.org
Cc: Daniel J Blueman <daniel.blueman@gmail.com>,
	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:34:30 +0200	[thread overview]
Message-ID: <4AB5DB06.1090100@klingt.org> (raw)
In-Reply-To: <1253401950.7587.7.camel@ben-desktop>

[-- Attachment #1: Type: text/plain, Size: 808 bytes --]

On 09/20/2009 01:12 AM, Ben Nizette wrote:
> 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/

i'd be curious, what effect does it have on userspace applications?
like, does it effect the wakeup latency of userspace (pthread)
mutexes/conditions or posix semaphores?

thnx, tim

-- 
tim@klingt.org
http://tim.klingt.org

Desperation is the raw material of drastic change. Only those who can
leave behind everything they have ever believed in can hope to escape.
  William S. Burroughs


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-09-20  7:35 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
2009-09-20  7:34       ` Tim Blechmann [this message]
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=4AB5DB06.1090100@klingt.org \
    --to=tim@klingt.org \
    --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