Messages in this thread | | | Date | Thu, 30 Jun 2005 19:52:54 -0700 (PDT) | Subject | Re: -mm -> 2.6.13 merge status (dropped patches?) | From | "David S. Miller" <> |
| |
From: Andrew Morton <akpm@osdl.org> Date: Thu, 30 Jun 2005 16:14:56 -0700
> Chuck Ebbert <76306.1226@compuserve.com> 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 > netdev@oss.sgi.com 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |