| 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 13 Aug 2013 09:53:50 +0300 From: David Shwatrz <dshwatrz@...il.com> To: Julia Lawall <julia.lawall@...6.fr> Cc: Francois Romieu <romieu@...zoreil.com>, grant.likely@...aro.org, rob.herring@...xeda.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, devicetree@...r.kernel.org Subject: Re: question about netif_rx Hello, Sorry. I still don't understand what checksum has to do with it. Does GRO depends on Rx/Tx checksum ? I don't think so. In the napi_gro_receive() we check that the device supports NETIF_F_GRO, but I don't see that we inspect checksum or that NETIF_F_GRO is depends on checksum. Can you please explain how checsum offload is related ? rgs David On Tue, Aug 13, 2013 at 9:29 AM, Julia Lawall <julia.lawall@...6.fr> wrote: > On Tue, 13 Aug 2013, Francois Romieu wrote: > >> Julia Lawall <julia.lawall@...6.fr> : >> > François Romieu <romieu@...zoreil.com> : >> [...] >> > > Can you send a netif_receive_skb replacement patch for it ? >> > >> > Just to be sure, I just replace netif_rx by netif_receive_skb, nothing >> > else? >> >> Yes. It should imho be fine with a comment incluing your analysis and a >> few words about the current state of checksum offloading support. > > I wouldn't know what to say about the checksum part. It is not supported > so I should use netif_receive_skb? > > thanks, > julia -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists