mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel J Blueman <daniel.blueman@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: tickless and HZ=1000 throughput advantage?
Date: Sat, 19 Sep 2009 18:50:13 +0100	[thread overview]
Message-ID: <6278d2220909191050l19f2a446r5ccf1907fd963096@mail.gmail.com> (raw)
In-Reply-To: <20090919165501.65d77294@infradead.org>

On Sat, Sep 19, 2009 at 3:55 PM, Arjan van de Ven <arjan@infradead.org> wrote:
> On Sat, 19 Sep 2009 15:47:24 +0100
> Daniel J Blueman <daniel.blueman@gmail.com> wrote:
>
>> On tickless kernels, is the general consensus that for non-embedded
>> systems, selecting HZ=1000 gives slightly more throughput in
>> particular situations than HZ=100 or 250, due to finer timer
>> intervals/granularity?
>
> it's not about throughput. It's about latency for some things....
> although now that select/poll and co use hrtimers it's not as critical
> anymore.
>
> the HZ timers aren't used much for anything time-critical nowadays.

Agreed. Do you think there is still a small case for moving to HZ=1000
(given it's effectively free) in situations like:

jiffies_to_transmit = port->baud?(1 + charsleft * 10 * HZ / port->baud):0;

<applying plausible figures>
(gdb) p (1 + 10 * 10 * 1000 / 38400) * 1
$3 = 3
(gdb) p (1 + 10 * 10 * 250 / 38400) * 4
$5 = 4

-> HZ=250 causes a 33% longer sleep than expected

perhaps?
-- 
Daniel J Blueman

  reply	other threads:[~2009-09-19 17:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19 14:47 Daniel J Blueman
2009-09-19 14:55 ` Arjan van de Ven
2009-09-19 17:50   ` Daniel J Blueman [this message]
2009-09-19 23:12     ` Ben Nizette
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=6278d2220909191050l19f2a446r5ccf1907fd963096@mail.gmail.com \
    --to=daniel.blueman@gmail.com \
    --cc=arjan@infradead.org \
    --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

all inboxes | Powered by JetHome®