netdev
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [patch 05/13] remove last_rx update from loopback device

from [David S. Miller] [Permanent Link][Original]
To: Rick Jones <rick.jones2@xxxxxx>
Subject: Re: [patch 05/13] remove last_rx update from loopback device
From: "David S. Miller" <davem@xxxxxxxxxxxxx>
Date: Tue, 15 Mar 2005 17:17:38 -0800
Cc: akpm@xxxxxxxx, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx, christoph@xxxxxxxxxx, nirajk@xxxxxxxxxxxxxx, christoph@xxxxxxxxxxx, Shai@xxxxxxxxxxxx
In-reply-to: <42378617.3080600@xxxxxx>
References: <200503152222.j2FMMbhG016805@xxxxxxxxxxxxxxxxxxx> <423764A3.8030201@xxxxxxxxx> <20050315150809.579c5e85.akpm@xxxxxxxx> <20050315165345.735573de.davem@xxxxxxxxxxxxx> <42378617.3080600@xxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx 
On Tue, 15 Mar 2005 17:04:23 -0800
Rick Jones <rick.jones2@xxxxxx> wrote:

> Perhaps that is a driver-ing (since punning drive/driver seems to be the 
> order N 
> squared of the day) force behind the changes?

Every time the SGI guys with the 512 cpu machine find some shared
memory reference they think they can legitimately remove, they
try to do so.
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [patch 05/13] remove last_rx update from loopback device, Rick Jones
Next by Date:  Re: [patch 05/13] remove last_rx update from loopback device, Nivedita Singhvi
Previous by Thread:  Re: [patch 05/13] remove last_rx update from loopback device, Rick Jones
Next by Thread:  Re: [patch 05/13] remove last_rx update from loopback device, Nivedita Singhvi
Indexes:  [Date] [Thread] [Top] [All Lists]