From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: AF_PACKET mmap() v4... Date: Thu, 05 Nov 2015 08:17:59 -0800 Message-ID: <1446740279.4184.40.camel@edumazet-glaptop2.roam.corp.google.com> References: <20151105.000414.1682124328670738318.davem@davemloft.net> <4931220.z2MFa8LzkQ@wuerfel> <563B23C3.5070406@iogearbox.net> <1446723516.4184.33.camel@edumazet-glaptop2.roam.corp.google.com> <563B5202.1020207@iogearbox.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Arnd Bergmann , David Miller , netdev@vger.kernel.org, tklauser@distanz.ch To: Daniel Borkmann Return-path: Received: from mail-pa0-f46.google.com ([209.85.220.46]:36270 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1162166AbbKEQSC (ORCPT ); Thu, 5 Nov 2015 11:18:02 -0500 Received: by pacdm15 with SMTP id dm15so67316647pac.3 for ; Thu, 05 Nov 2015 08:18:01 -0800 (PST) In-Reply-To: <563B5202.1020207@iogearbox.net> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, 2015-11-05 at 13:56 +0100, Daniel Borkmann wrote: > On 11/05/2015 12:38 PM, Eric Dumazet wrote: > > If I am not mistaken, af_packet also lacks the ability to properly set > > skb->protocol > > > > I noticed this using trafgen on a bonding device, when I did my SYNFLOOD > > tests for TCP listener rewrite. > > > > The bonding hash function might uses flow dissector, but as this flow > > dissection depends on skb->protocol, all the traffic is directed on a > > single slave. > > Right, if I see this correctly, when you trigger the flushing of TX_RING > via sendmsg(), one can hand over a sockaddr_ll, where we infer sll_protocol > and tag every skb's skb->protocol with that in tpacket_fill_skb() for the > current flushing run. Otherwise, we use the po->num specified at socket > creation / bind time for everything (trafgen case). > > If needed on a per skb basis, perhaps we could map some tpacket_hdr{,2} > member that is not used from TX_RING side (perhaps union on tp_snaplen)? If po->num is 0 (as in trafgen case), we could also get the proto from Ethernet header provided by the user. The skb_probe_transport_header() call from tpacket_fill_skb() is useless in the current kernel. Let say an application wants to mix IPv6 and IPv4 packets, using a single TX ring....