netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Welte <laforge@gnumonks.org>
To: Andi Kleen <ak@suse.de>
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: packet re-ordering on SMP machines.
Date: Sun, 15 Sep 2002 10:42:01 +0200	[thread overview]
Message-ID: <20020915104201.D3810@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20020827151317.A3389@wotan.suse.de>; from ak@suse.de on Tue, Aug 27, 2002 at 03:13:17PM +0200

[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]

On Tue, Aug 27, 2002 at 03:13:17PM +0200, Andi Kleen wrote:
> 
> On Tue, Aug 27, 2002 at 05:06:30PM +0400, A.N.Kuznetsov wrote:
> > Hello!
> > 
> > > Of course. The only problem is that the clock can be non mononotonous 
> > > sometimes and not be in sync with gettimeofday, but at least the kernel 
> > > users of packet timestamps do not care.
> > 
> > What kernel users? Where did you find them? :-)
> 
> Hmm, I thought TCP used it, but it seems to use jiffies directly.
> 
> Ok, no kernel users then. Not sure about sunrpc and out of tree stuff
> like SCTP.

The iptables ULOG target passes the skb receive timestamp to userspace, where
it is (depending on local ulogd configuration) written in logging/accounting
databases. (ULOG is in the kernel tree).  

The issue is that ULOG is batching multiple packets (or parts of packets) into
one netlink message sent to userspace.  If userspace would make a timestamp,
it would be very inaccurate.

There is at least one more iptables extension (out of the kernel tree) using
it - but I wouldn't consider this as important.

> -Andi

-- 
Live long and prosper
- Harald Welte / laforge@gnumonks.org               http://www.gnumonks.org/
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M+ 
V-- PS++ PE-- Y++ PGP++ t+ 5-- !X !R tv-- b+++ !DI !D G+ e* h--- r++ y+(*)

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2002-09-15  8:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.30.0208251149320.29461-100000@shell.cyberus.ca>
2002-08-25 18:32 ` packet re-ordering on SMP machines 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 [this message]
2002-09-15 21:55                       ` Alexey Kuznetsov
2002-08-27 17:22                 ` Cheng Jin
2002-08-27 17:33                   ` Andi Kleen
2002-08-27 19:43               ` Xiaoliang (David) Wei
2002-08-25 15:56 jamal

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=20020915104201.D3810@sunbeam.de.gnumonks.org \
    --to=laforge@gnumonks.org \
    --cc=ak@suse.de \
    --cc=kuznet@ms2.inr.ac.ru \
    --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).