From: john stultz <johnstul@us.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: lkml <linux-kernel@vger.kernel.org>, ia64 <linux-ia64@vger.kernel.org>
Subject: Re: gettimeofday nanoseconds patch (makes it possible for the
Date: Wed, 14 Jul 2004 21:15:40 +0000 [thread overview]
Message-ID: <1089839740.1388.230.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0407141323530.15874@schroedinger.engr.sgi.com>
On Wed, 2004-07-14 at 13:28, Christoph Lameter wrote:
> > None the less, I do understand the desire for the change (and am working
> > to address it in 2.7), so could you at least use a better name then
> > gettimeofday()? Maybe get_ns_time() or something? Its just too similar
> > to do_gettimeofday and the syscall gettimeofday().
>
> Right. I had it named getnstimeofday before but the feeling was that the
> patch should not introduce a new name. Any approach that would allow
> progress on the issue would be fine with me.
Fair enough. getnstimeofday() sounds good enough for me.
> > Really, I feel the cleaner method is to fix do_gettimeofday() so it
> > returns a timespec and then convert it to a timeval in
> > sys_gettimeofday(). However this would add overhead to the syscall, so I
> > doubt folks would go for it.
>
> do_gettimeofday is used all over the linux kernel for a variety of
> purposes and lots of code depends on the presence of a timeval struct.
Indeed, it would be a decent amount of work to clean that up as well.
thanks
-john
next prev parent reply other threads:[~2004-07-14 21:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 16:41 gettimeofday nanoseconds patch (makes it possible for the posix-timer Christoph Lameter
2004-07-14 20:09 ` gettimeofday nanoseconds patch (makes it possible for the john stultz
2004-07-14 20:28 ` Christoph Lameter
2004-07-14 21:14 ` David Mosberger
2004-07-14 21:15 ` john stultz [this message]
2004-07-15 0:08 ` Christoph Lameter
2004-07-15 0:48 ` john stultz
2004-07-15 1:16 ` David Mosberger
2004-07-15 1:35 ` john stultz
2004-07-15 3:57 ` David Mosberger
2004-07-15 15:31 ` Christoph Lameter
2004-07-15 16:14 ` john stultz
2004-07-15 17:03 ` Christoph Lameter
2004-07-15 17:18 ` john stultz
2004-07-15 22:59 ` gettimeofday nanoseconds patch (makes it possible for the posix-timer George Anzinger
2004-07-16 2:44 ` gettimeofday nanoseconds patch (makes it possible for the Christoph Lameter
2004-07-14 21:09 ` gettimeofday nanoseconds patch (makes it possible for the posix-timer functions to return higher Matthew Wilcox
2004-07-14 21:27 ` gettimeofday nanoseconds patch (makes it possible for the Christoph Lameter
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=1089839740.1388.230.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=clameter@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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