public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, mingo@elte.hu
Subject: Re: [patch 0/2] Introduce round_jiffies() to save spurious wakeups
Date: Wed, 11 Oct 2006 18:23:31 +0100	[thread overview]
Message-ID: <20061011172331.GA13099@infradead.org> (raw)
In-Reply-To: <1160496165.3000.308.camel@laptopd505.fenrus.org>

On Tue, Oct 10, 2006 at 06:02:45PM +0200, Arjan van de Ven wrote:
> Hi,
> 
> the following 2 patches will introduce the round_jiffies() api and users
> thereof. 
> 
> The general idea is that by rounding the jiffies for certain timers to
> the next whole second will make those timers all happen at the same
> time; and thus reduce the number of times the cpu has to wake up to
> service timers (this assumes a tickless kernel)
> 
> Obviously only timers where the exact time of firing isn't so important
> can do this; several of the recurring "always live" timers of the kernel
> are of this kind, they want "about once a second" or "about once every 4
> seconds" and such, and don't really care about the exact jiffy in which
> they fire.
> 
> An alternative would have been to introduce mod_timer_rounded() or
> somesuch APIs (but there's many variants that take jiffies); I feel that
> an explicit caller based rounding actually is quite reasonable.

I think the API you proposed is horrible.  Having jiffies exposed in
ani API is a mistake, and adding more makes this problem worse.  I'd suggest
to start with Alan's patches that add a timer variant that takes a miliseconds
argument instead of jiffies and add a _rounded varaint to it that has
a new parameter that specifies the precision.


  parent reply	other threads:[~2006-10-11 17:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 16:02 [patch 0/2] Introduce round_jiffies() to save spurious wakeups Arjan van de Ven
2006-10-10 16:03 ` [patch 1/2] round_jiffies infrastructure Arjan van de Ven
2006-10-10 16:04   ` [patch 2/2] round_jiffies users Arjan van de Ven
2006-10-10 16:47     ` Ingo Oeser
2006-10-10 16:59       ` Arjan van de Ven
2006-10-10 22:47     ` Paul Dickson
2006-10-10 23:52       ` Arjan van de Ven
2006-10-10 18:56   ` [patch 1/2] round_jiffies infrastructure Andrew Morton
2006-10-10 20:48     ` Arjan van de Ven
2006-10-16 13:42   ` Andi Kleen
2006-10-11 17:23 ` Christoph Hellwig [this message]
2006-10-11 17:54   ` [patch 0/2] Introduce round_jiffies() to save spurious wakeups Arjan van de Ven
2006-10-12 19:02     ` Christoph Hellwig

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=20061011172331.GA13099@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@osdl.org \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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