From: Ben Greear <greearb@candelatech.com>
To: Mitchell Blank Jr <mitch@sfgoth.com>
Cc: "David S. Miller" <davem@redhat.com>, netdev@oss.sgi.com
Subject: Re: do_gettimeofday
Date: Fri, 03 Oct 2003 09:42:19 -0700 [thread overview]
Message-ID: <3F7DA6EB.4040200@candelatech.com> (raw)
In-Reply-To: <20031003092617.GI42593@gaz.sfgoth.com>
Mitchell Blank Jr wrote:
> David S. Miller wrote:
>
>>There is the weird issue (with both the sparc64 example and your's
>>here) of whether we should care about what happens when settimeofday()
>>occurs. We probably shouldn't worry about it... as it gives weird
>>results even currently.
>
>
> Nah. If anything you'll get better results since you're computing
> the timeval later.
>
> This is another argument for caching the computation though - otherwise
> a settimeofday() could cause the packet timestamp to change drasically
> from one observation to the next :-)
It would also be nice to be able to set a flag on raw sockets to just have the 'raw' timestamp passed
up to user-space. In many cases, the relative timestamp may be all that is needed,
and user-space could optimize the conversion to gettimeofday as needed.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2003-10-03 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 18:32 do_gettimeofday Steve Modica
2003-10-02 19:29 ` do_gettimeofday Andi Kleen
2003-10-02 19:56 ` do_gettimeofday Stephen Hemminger
2003-10-02 20:46 ` do_gettimeofday Mitchell Blank Jr
2003-10-03 7:41 ` do_gettimeofday David S. Miller
2003-10-03 8:26 ` do_gettimeofday Mitchell Blank Jr
2003-10-03 8:27 ` do_gettimeofday David S. Miller
2003-10-03 8:48 ` do_gettimeofday Mitchell Blank Jr
2003-10-03 8:52 ` do_gettimeofday David S. Miller
2003-10-03 9:26 ` do_gettimeofday Mitchell Blank Jr
2003-10-03 9:23 ` do_gettimeofday David S. Miller
2003-10-03 16:42 ` Ben Greear [this message]
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=3F7DA6EB.4040200@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@redhat.com \
--cc=mitch@sfgoth.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).