| To: | Andi Kleen <ak@xxxxxxx> |
|---|---|
| Subject: | Re: packet re-ordering on SMP machines. |
| From: | Cheng Jin <chengjin@xxxxxxxxxxxxxx> |
| Date: | Tue, 27 Aug 2002 10:22:13 -0700 (PDT) |
| Cc: | jamal <hadi@xxxxxxxxxx>, "Xiaoliang (David) Wei" <weixl@xxxxxxxxxxx>, Ben Greear <greearb@xxxxxxxxxxxxxxx>, Cheng Hu <chenghu@xxxxxxxxxxxxxx>, Steven Low <slow@xxxxxxxxxxxxxx>, "netdev@xxxxxxxxxxx" <netdev@xxxxxxxxxxx> |
| In-reply-to: | <20020827142004.C4358@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
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 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) 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. Thanks, Cheng |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Lse-tech] Re: (RFC): SKB Initialization, jamal |
|---|---|
| Next by Date: | Re: packet re-ordering on SMP machines., Andi Kleen |
| Previous by Thread: | Re: packet re-ordering on SMP machines., kuznet |
| Next by Thread: | Re: packet re-ordering on SMP machines., Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |