netdev - Re: [RFC PATCH net-next-2.6] gro: drivers should feed GRO only with TCP packets

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100901105519.603492cf@nehalam>
Date:	Wed, 1 Sep 2010 10:55:19 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	David Miller <davem@...emloft.net>
Cc:	eric.dumazet@...il.com, netdev@...r.kernel.org
Subject: Re: [RFC PATCH net-next-2.6] gro: drivers should feed GRO only with
 TCP packets

On Wed, 01 Sep 2010 10:48:05 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:

> From: Stephen Hemminger <shemminger@...tta.com>
> Date: Wed, 1 Sep 2010 10:42:35 -0700
> 
> > There was talk of doing GRO for UDP as well but it never
> > got implemented. 
> 
> I suppose the most direct application would be for IP fragmentation.
> 
> In fact I could see that working very well.
> 
> But for non-fragmented UDP... I can't see much value to that.
> 
> We'd have to preserve the packet boundaries, and process each chunk of
> data as one packet at a time within those boundaries, to retain
> datagram recvmsg() semantics.

I was thinking for fragmented UDP, which still unfortunately
gets used. 
--
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