netdev
[Top] [All Lists]

Re: Route cache performance under stress

To: ralph+d@xxxxxxxxx, ralph@xxxxxxxxx
Subject: Re: Route cache performance under stress
From: "David S. Miller" <davem@xxxxxxxxxx>
Date: Tue, 10 Jun 2003 17:58:13 -0700 (PDT)
Cc: Robert.Olsson@xxxxxxxxxxx, hadi@xxxxxxxxxxxxxxxx, xerox@xxxxxxxxxx, sim@xxxxxxxxxxxxx, fw@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.51.0306102030530.12166@xxxxxxxxxxxx>
References: <Pine.LNX.4.51.0306101956520.7801@xxxxxxxxxxxx> <20030610.165759.78731321.davem@xxxxxxxxxx> <Pine.LNX.4.51.0306102030530.12166@xxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
   From: Ralph Doncaster <ralph@xxxxxxxxx>
   Date: Tue, 10 Jun 2003 20:41:13 -0400 (EDT)

   On Tue, 10 Jun 2003, David S. Miller wrote:
   
   > Guess you never run tcpdump nor use packet schedulers.
   
   So because some (in the case of a core router almost none) of the packets
   will need a timestamp, you do it for every single one of them?

In order to be accurate, we must obtain the timestamp
exactly when we receive the packet.

But until we know that the packet is for us or not (which
requires a route lookup), we don't know if we actually need
the timestamp or not.

This is not some arbitrary thing, this is how you have to
implement this.  It's not like we said "screw everyone,
let's get a timestamp all the time whether we need it or
not." :-)


<Prev in Thread] Current Thread [Next in Thread>