From: Ben Greear <greearb@candelatech.com>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-os@analogic.com, Adrian Bunk <bunk@stusta.de>,
Kyle Moffett <mrmacman_g4@mac.com>,
"Gilbert, John" <JGG@dolby.com>,
linux-kernel@vger.kernel.org
Subject: Re: Illegal use of reserved word in system.h
Date: Thu, 19 May 2005 10:40:55 -0700 [thread overview]
Message-ID: <428CCFA7.6010206@candelatech.com> (raw)
In-Reply-To: <428CCE87.2010308@nortel.com>
Chris Friesen wrote:
> Ben Greear wrote:
>
>> It can be helpful to know what HZ you are running at, for instance if
>> you care
>> very much about the (average) precision of a select/poll timeout.
>
>
> If you move the binary to a different system (or upgrade the kernel, for
> that matter) the assumptions can be totally wrong.
>
> This should be checked at runtime, not compile time.
If course...that is why I like the idea of some system call or standard API
to get the information.
Ben
>
> Chris
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2005-05-19 17:44 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 19:07 Gilbert, John
2005-05-18 19:53 ` Adrian Bunk
2005-05-19 2:22 ` Kyle Moffett
2005-05-19 11:28 ` Adrian Bunk
2005-05-19 12:19 ` Richard B. Johnson
2005-05-19 12:27 ` Arjan van de Ven
2005-05-19 12:47 ` Maciej W. Rozycki
2005-05-19 13:01 ` Richard B. Johnson
2005-05-19 13:47 ` Steven Rostedt
2005-05-19 14:06 ` Andreas Schwab
2005-05-19 14:15 ` Steven Rostedt
2005-05-19 14:36 ` Richard B. Johnson
2005-05-19 15:19 ` Andreas Schwab
2005-05-19 15:56 ` Steven Rostedt
2005-05-19 16:03 ` Richard B. Johnson
2005-05-19 15:58 ` Richard B. Johnson
2005-05-19 16:22 ` Steven Rostedt
2005-05-19 17:06 ` Richard B. Johnson
2005-05-19 17:36 ` Steven Rostedt
2005-05-19 14:43 ` Maciej W. Rozycki
2005-05-19 14:59 ` Steven Rostedt
2005-05-20 12:23 ` Maciej W. Rozycki
2005-05-19 14:53 ` Arjan van de Ven
2005-05-19 14:58 ` Maciej W. Rozycki
2005-05-19 15:06 ` Arjan van de Ven
2005-05-19 13:56 ` Steven Rostedt
2005-05-19 17:30 ` Ben Greear
2005-05-19 17:36 ` Chris Friesen
2005-05-19 17:40 ` Ben Greear [this message]
2005-05-19 22:14 ` Andreas Schwab
2005-05-19 22:30 ` J.A. Magallon
2005-05-19 22:41 ` Russell King
2005-05-19 23:10 ` J.A. Magallon
2005-05-20 0:01 ` Jeff Woods
2005-05-20 9:27 ` Helge Hafting
2005-05-20 16:47 ` Lee Revell
2005-05-20 16:56 ` Ben Greear
2005-05-18 23:42 ` Andi Kleen
2005-05-18 23:59 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2005-05-20 17:30 Gilbert, John
2005-05-19 20:18 Gilbert, John
2005-05-19 1:51 Gilbert, John
2005-05-18 21:31 Gilbert, John
2005-05-19 17:37 ` Alan Cox
2005-05-20 11:49 ` Dave Airlie
2005-05-20 16:42 ` Alan Cox
2005-05-18 18:23 Gilbert, John
2005-05-18 19:02 ` Adrian Bunk
2005-05-18 19:32 ` Richard B. Johnson
2005-05-19 1:06 ` rdunlap
2005-05-18 0:51 Gilbert, John
2005-05-18 0:57 ` Lee Revell
2005-05-18 1:19 ` Chris Wedgwood
2005-05-18 2:51 ` Steven Rostedt
2005-05-18 4:12 ` Willy Tarreau
2005-05-18 10:06 ` Patrick McFarland
2005-05-18 10:49 ` Coywolf Qi Hunt
2005-05-18 11:12 ` Richard B. Johnson
2005-05-18 21:52 ` Matan Peled
2005-05-19 11:03 ` Richard B. Johnson
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=428CCFA7.6010206@candelatech.com \
--to=greearb@candelatech.com \
--cc=JGG@dolby.com \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=mrmacman_g4@mac.com \
/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
Powered by JetHome