lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 5 Jul 2007 19:45:35 +0400 From: Evgeniy Polyakov <johnpol@....mipt.ru> To: Jan-Bernd Themann <ossthema@...ibm.com> Cc: netdev <netdev@...r.kernel.org>, Jeff Garzik <jeff@...zik.org>, Christoph Raisch <raisch@...ibm.com>, Jan-Bernd Themann <themann@...ibm.com>, linux-kernel <linux-kernel@...r.kernel.org>, linux-ppc <linuxppc-dev@...abs.org>, Marcus Eder <meder@...ibm.com>, Thomas Klein <tklein@...ibm.com>, Stefan Roscher <stefan.roscher@...ibm.com>, Christoph Hellwig <hch@...radead.org> Subject: Re: [PATCH 2/2] eHEA: Receive SKB Aggregation, generic LRO helper functions On Thu, Jul 05, 2007 at 04:24:46PM +0200, Jan-Bernd Themann (ossthema@...ibm.com) wrote: > > I've couple of comments on the driver, but mainly the fact of decreased > > CPU usage itself - what was the magnitude of the win with this driver, > > it looks like because of per-packet receive code path invocation is the > > place of the latency... > > Your implementation looks generic enough to be used by any driver, don't > > you want to push it separately from eHEA driver? > > > > We can try to come up with a generic file with these helperfunctions. > What do you think about putting them into /net/ipv4/inet_lro.c and > /include/linux/inet_lro.h ? The more I think, the more it looks as appropriate to be used by all hardware drivers with proper API. As far as I recall this is third implementation in the linux drivers :) -- Evgeniy Polyakov - 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