From: Kyle Moffett <mrmacman_g4@mac.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: James Bruce <bruce@andrew.cmu.edu>,
David Lang <david.lang@digitalinsight.com>,
Steven Rostedt <rostedt@goodmis.org>,
johnstul@us.ibm.com, george@mvista.com, mingo@elte.hu,
akpm@osdl.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
ray-gmail@madrabbit.org, Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [patch 00/43] ktimer reworked
Date: Wed, 7 Dec 2005 09:15:32 -0500 [thread overview]
Message-ID: <0EA7F687-BB3F-4CC2-953E-EEA057F6FC44@mac.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0512071319320.1609@scrub.home>
On Dec 07, 2005, at 07:34, Roman Zippel wrote:
> Hi,
>
> On Wed, 7 Dec 2005, James Bruce wrote:
>> And that's the whole *point* about how we got here. Let the low
>> resolution, low lifetime timeouts stay on the timer wheel, and
>> make a new approach that specializes in handling longer lifetime,
>> higher resolution timers. That's ktimers in a nutshell. You seem
>> to be arguing for it rather than against it.
>
> I do, just without the focus on the lifetime, which is really
> unimportant for most kernel developers.
It _is_ important. Not because kernel developers do care about it,
but because it's important for reasons of its own and therefore they
should. Networking timeouts and highres audio timers are two _VERY_
different applications of "do this thing then", and kernel developers
should be made aware of them. If you disagree, please explain in
detail exactly why you think the lifetime is unimportant. I have yet
to see an email regarding this, and I've searched the archives pretty
carefully, in addition to watching this thread.
Cheers,
Kyle Moffett
--
I lost interest in "blade servers" when I found they didn't throw
knives at people who weren't supposed to be in your machine room.
-- Anthony de Boer
next prev parent reply other threads:[~2005-12-07 14:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 23:56 Thomas Gleixner
2005-12-01 0:41 ` Andrew Morton
2005-12-01 2:19 ` Ingo Molnar
2005-12-01 3:32 ` Roman Zippel
2005-12-01 3:57 ` Kyle Moffett
2005-12-01 15:40 ` Roman Zippel
2005-12-01 16:22 ` Ray Lee
2005-12-01 16:51 ` Russell King
2005-12-01 17:44 ` Roman Zippel
2005-12-01 19:08 ` Steven Rostedt
2005-12-01 21:11 ` Roman Zippel
2005-12-01 22:03 ` Steven Rostedt
2005-12-02 0:29 ` Roman Zippel
2005-12-02 0:41 ` Kyle Moffett
2005-12-02 0:58 ` john stultz
2005-12-02 1:01 ` Roman Zippel
2005-12-02 1:09 ` Kyle Moffett
2005-12-02 1:24 ` Roman Zippel
2005-12-02 1:47 ` David Lang
2005-12-02 14:43 ` Roman Zippel
2005-12-02 15:41 ` Kyle Moffett
2005-12-07 9:35 ` James Bruce
2005-12-07 12:34 ` Roman Zippel
2005-12-07 14:15 ` Kyle Moffett [this message]
2005-12-07 15:03 ` Roman Zippel
2005-12-07 14:17 ` Steven Rostedt
2005-12-08 15:43 ` James Bruce
2005-12-02 2:51 ` Steven Rostedt
2005-12-04 1:28 ` Andrew James Wade
2005-12-05 19:40 ` Roman Zippel
2005-12-06 2:46 ` Andrew James Wade
2005-12-01 20:24 ` Andrew Morton
2005-12-01 21:19 ` Ingo Molnar
2005-12-01 21:51 ` Andrew Morton
2005-12-01 22:13 ` Kyle Moffett
2005-12-01 22:15 ` Christoph Hellwig
2005-12-02 0:02 ` Thomas Gleixner
2005-12-02 0:36 ` Kyle Moffett
2005-12-02 1:06 ` Andrew Morton
2005-12-02 14:42 ` John Stoffel
2005-12-02 2:21 ` Steven Rostedt
2005-12-02 0:46 ` Roman Zippel
2005-12-01 16:52 ` Roman Zippel
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=0EA7F687-BB3F-4CC2-953E-EEA057F6FC44@mac.com \
--to=mrmacman_g4@mac.com \
--cc=akpm@osdl.org \
--cc=bruce@andrew.cmu.edu \
--cc=david.lang@digitalinsight.com \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ray-gmail@madrabbit.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.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®