From: Andrew Morton <[email protected]>
Date: Thu, 30 Jun 2005 16:14:56 -0700
> Chuck Ebbert <[email protected]> wrote:
> >
> > What happened to:
> >
> > remove-last_rx-update-from-loopback-device.patch
>
> Davem rejected it. hm, I can't find the email trail - it was cc'ed to
> [email protected] mid-March, but nothing seems to have been sent back.
Every network device must reliably set ->last_rx, there are parts
of the kernel which depend upon this attribute having an accurate
value.
The bonding driver is one example. And whilst one can argue that
loopback is unlikely to be used as part of a bond, it's massively
better from a consistency perspective if this invariant can be
relied upon across all networking drivers.
In short, the NUMA scalability hacks to loopback have gotten out
of control, and we need to stop this madness somewhere.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |