From: Andrew Morton <akpm@linux-foundation.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, tglx@tglx.de, mingo@elte.hu,
Cyrill Gorcunov <gorcunov@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] timers: Introduce the concept of timer slack for legacy timers
Date: Wed, 13 Jan 2010 22:07:55 -0800 [thread overview]
Message-ID: <20100113220755.7ad6286f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100113214528.41e2de4a@infradead.org>
On Wed, 13 Jan 2010 21:45:28 -0800 Arjan van de Ven <arjan@infradead.org> wrote:
> On Wed, 13 Jan 2010 13:52:19 -0800
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > I suppose this could be inlined.
>
> .. and then I expand it a bit in a few weeks and guess who complains an
> inline gets too big ? ;-)
>
Me!
You're proposing that we include trivially-fixed overhead to every
Linux machine in the world to save ourselves 15 minutes effort? Nope,
bad tradeoff.
> >
> > But the set_timer_slack() interface has no callers. Perhaps it
> > should?
>
> I have some callers pending, and I thought I posted those to lkml but
> maybe I did not.
hm.
Have you any feeling for how much power this sort of thing saves? I
guess "change in interrupts per minute" would be easy to measure.
next prev parent reply other threads:[~2010-01-14 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 21:37 [PATCH] timers: Introduce the concept of timer slack for legacy timers Arjan van de Ven
2010-01-13 21:52 ` Andrew Morton
2010-01-14 5:45 ` Arjan van de Ven
2010-01-14 6:07 ` Andrew Morton [this message]
2010-01-14 9:53 ` 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=20100113220755.7ad6286f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tglx@tglx.de \
/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