Re: Network performance degradation from 2.6.11.12 to 2.6.16.20
From: David Miller
Date: Mon Sep 18 2006 - 17:23:33 EST
From: Alexey Kuznetsov <kuznet@xxxxxxxxxxxxx>
Date: Tue, 19 Sep 2006 01:03:21 +0400
> 1. It even does not disable possibility to record timestamp inside
> driver, which Alan was afraid of. The sequence is:
>
> if (!skb->tstamp.off_sec)
> net_timestamp(skb);
>
> 2. Maybe, netif_rx() should continue to get timestamp in netif_rx().
>
> 3. NAPI already introduced almost the same inaccuracy. And it is really
> silly to waste time getting timestamp in netif_receive_skb() a few
> moments before the packet is delivered to a socket.
>
> 4. ...but clock source, which takes one of top lines in profiles
> must be repaired yet. :-)
Ok, ok, but don't we have queueing disciplines that need the timestamp
even on ingress?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/