[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080827.174855.126675086.davem@davemloft.net>
Date: Wed, 27 Aug 2008 17:48:55 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: nickpiggin@...oo.com.au
Cc: andi@...stfloor.org, rick.jones2@...com, johnpol@....mipt.ru,
dada1@...mosbay.com, denys@...p.net.lb, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: loaded router, excessive getnstimeofday in oprofile
From: Nick Piggin <nickpiggin@...oo.com.au>
Date: Thu, 28 Aug 2008 10:45:03 +1000
> On Thursday 28 August 2008 08:39, Andi Kleen wrote:
> > On Wed, Aug 27, 2008 at 03:18:24PM -0700, David Miller wrote:
> > > From: Andi Kleen <andi@...stfloor.org>
> > > Date: Wed, 27 Aug 2008 18:27:35 +0200
> > >
> > > > > Those banks really want to crank down on latency - to the point they
> > > > > start disabling interrupt coalescing. I bet they'd toss anything out
> > > > > they could to shave another microsecond.
> > > >
> > > > This change would actually likely lower their latency.
> > >
> > > They want the timestamps, but they want it to match when the packet
> > > arrived at their system as closely as is reasonably possible.
> >
> > Then they should use hardware time stamps which are increasingly
> > available (e.g. current Intel e1000 design has them and I expect
> > others too).
>
> Would it make sense to make a new option for these socket timestamps
> and encourage some apps move over to it?
We don't have support to using these specific hardware provided timestamps
sources yet, so it's kind of premature to recommend the facility to
applications. :)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists