From: Andi Kleen <ak@suse.de>
To: Cheng Jin <chengjin@cs.caltech.edu>
Cc: Andi Kleen <ak@suse.de>, jamal <hadi@cyberus.ca>,
"Xiaoliang (David) Wei" <weixl@caltech.edu>,
Ben Greear <greearb@candelatech.com>,
Cheng Hu <chenghu@cs.caltech.edu>,
Steven Low <slow@cs.caltech.edu>,
"netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: Re: packet re-ordering on SMP machines.
Date: Tue, 27 Aug 2002 19:33:03 +0200 [thread overview]
Message-ID: <20020827193303.B4971@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33L0.0208271011040.27776-100000@orchestra.cs.caltech.edu>
On Tue, Aug 27, 2002 at 10:22:13AM -0700, Cheng Jin wrote:
> Hi, Andi,
>
> > Quick fix is to just use gettimeoffset in netif_rx again. Should
> > be fine for you.
>
> There doesn't appear to be a function called gettimeoffset in 2.4.18
> anymore. The closest I found was do_fast_gettimeoffset in
> "arch/i386/kernel/time.c" This appears to be the unlocked version that
Yes, I mean do_fast_gettimeoffset.
> you are referring to, except I can't tell why the higher 32 bits (edx) of
> the timestamp isn't used. (maybe the asm code takes care of it, but it seems
> that the result is stored in edx so)
32bit precision are probably enough for this.
>
> What you said about a light-weight gettime function makes sense. For our
> purpose of timing RTTs, any gettime function with a resolution higher than
> 1 ms will probably be enough. The time doesn't need to be in exactly in sync
> with the one obtained from the locking version of the gettime function.
TSC should be fine then.
-Andi
next prev parent reply other threads:[~2002-08-27 17:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-25 15:56 packet re-ordering on SMP machines jamal
2002-08-25 18:32 ` Ben Greear
2002-08-26 0:52 ` jamal
2002-08-26 4:34 ` Ben Greear
2002-08-26 11:20 ` jamal
2002-08-26 23:03 ` Xiaoliang (David) Wei
2002-08-26 23:20 ` Ben Greear
2002-08-27 10:59 ` jamal
2002-08-27 11:12 ` Andi Kleen
2002-08-27 12:05 ` jamal
2002-08-27 12:20 ` Andi Kleen
2002-08-27 13:06 ` kuznet
2002-08-27 13:13 ` Andi Kleen
2002-08-27 13:24 ` kuznet
2002-09-15 8:42 ` Harald Welte
2002-09-15 21:55 ` Alexey Kuznetsov
2002-08-27 17:22 ` Cheng Jin
2002-08-27 17:33 ` Andi Kleen [this message]
2002-08-27 19:43 ` Xiaoliang (David) Wei
-- strict thread matches above, loose matches on Subject: below --
2002-08-25 15:56 jamal
2002-08-25 8:01 Manfred Spraul
2002-08-25 7:18 Ben Greear
2002-08-25 7:07 ` David S. Miller
2002-08-25 14:41 ` Alan Cox
2002-08-25 17:00 ` Ben Greear
2002-08-25 20:44 ` Alan Cox
2002-08-25 22:49 ` David S. Miller
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=20020827193303.B4971@wotan.suse.de \
--to=ak@suse.de \
--cc=chenghu@cs.caltech.edu \
--cc=chengjin@cs.caltech.edu \
--cc=greearb@candelatech.com \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.com \
--cc=slow@cs.caltech.edu \
--cc=weixl@caltech.edu \
/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.