From: Andrew Morton <akpm@osdl.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: ray-gmail@madrabbit.org, zippel@linux-m68k.org,
mrmacman_g4@mac.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, mingo@elte.hu, george@mvista.com,
johnstul@us.ibm.com
Subject: Re: [patch 00/43] ktimer reworked
Date: Thu, 1 Dec 2005 12:24:55 -0800 [thread overview]
Message-ID: <20051201122455.4546d1da.akpm@osdl.org> (raw)
In-Reply-To: <20051201165144.GC31551@flint.arm.linux.org.uk>
Russell King <rmk+lkml@arm.linux.org.uk> wrote:
>
> rmk, also a native English speaker, agrees with Ray, Thomas and Ingo.
> As does dictionary.reference.com's definitions of timeout and timer:
>
> timeout
>
> A period of time after which an error condition is raised if some event
> has not occured. A common example is sending a message. If the receiver
> does not acknowledge the message within some preset timeout period, a
> transmission error is assumed to have occured.
>
> timer
>
> a timepiece that measures a time interval and signals its end
>
> Hence, timers have the implication that they are _expected_ to expire.
> Timeouts have the implication that their expiry is an exceptional
> condition.
Well timer_lists get around the problem quite neatly by handling both
situations. In a way which has been learned by thousands of developers
over many years.
The whole concept of separating "timers" from "timeouts" seems a step
backward to me. A large one. Why was it done, and can it be undone?
next prev parent reply other threads:[~2005-12-01 20:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 23:56 [patch 00/43] ktimer reworked 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
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 [this message]
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=20051201122455.4546d1da.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mrmacman_g4@mac.com \
--cc=ray-gmail@madrabbit.org \
--cc=rmk+lkml@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.