From: Jesper Dangaard Brouer <brouer@redhat.com> To: "Machulsky, Zorik" <zorik@amazon.com> Cc: "Jubran, Samih" <sameehj@amazon.com>, "davem@davemloft.net" <davem@davemloft.net>, "netdev@vger.kernel.org" <netdev@vger.kernel.org>, "Woodhouse, David" <dwmw@amazon.co.uk>, "Matushevsky, Alexander" <matua@amazon.com>, "Bshara, Saeed" <saeedb@amazon.com>, "Wilson, Matt" <msw@amazon.com>, "Liguori, Anthony" <aliguori@amazon.com>, "Bshara, Nafea" <nafea@amazon.com>, "Tzalik, Guy" <gtzalik@amazon.com>, "Belgazal, Netanel" <netanel@amazon.com>, "Saidi, Ali" <alisaidi@amazon.com>, "Herrenschmidt, Benjamin" <benh@amazon.com>, "Kiyanovski, Arthur" <akiyano@amazon.com>, "Daniel Borkmann" <borkmann@iogearbox.net>, brouer@redhat.com, "Toke Høiland-Jørgensen" <toke@redhat.com>, "Ilias Apalodimas" <ilias.apalodimas@linaro.org>, "Alexei Starovoitov" <alexei.starovoitov@gmail.com>, "Jakub Kicinski" <jakub.kicinski@netronome.com>, "xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org> Subject: XDP multi-buffer incl. jumbo-frames (Was: [RFC V1 net-next 1/1] net: ena: implement XDP drop support) Date: Wed, 26 Jun 2019 10:38:29 +0200 Message-ID: <20190626103829.5360ef2d@carbon> (raw) In-Reply-To: <A658E65E-93D2-4F10-823D-CC25B081C1B7@amazon.com> On Tue, 25 Jun 2019 03:19:22 +0000 "Machulsky, Zorik" <zorik@amazon.com> wrote: > On 6/23/19, 7:21 AM, "Jesper Dangaard Brouer" <brouer@redhat.com> wrote: > > On Sun, 23 Jun 2019 10:06:49 +0300 <sameehj@amazon.com> wrote: > > > This commit implements the basic functionality of drop/pass logic in the > > ena driver. > > Usually we require a driver to implement all the XDP return codes, > before we accept it. But as Daniel and I discussed with Zorik during > NetConf[1], we are going to make an exception and accept the driver > if you also implement XDP_TX. > > As we trust that Zorik/Amazon will follow and implement XDP_REDIRECT > later, given he/you wants AF_XDP support which requires XDP_REDIRECT. > > Jesper, thanks for your comments and very helpful discussion during > NetConf! That's the plan, as we agreed. From our side I would like to > reiterate again the importance of multi-buffer support by xdp frame. > We would really prefer not to see our MTU shrinking because of xdp > support. Okay we really need to make a serious attempt to find a way to support multi-buffer packets with XDP. With the important criteria of not hurting performance of the single-buffer per packet design. I've created a design document[2], that I will update based on our discussions: [2] https://github.com/xdp-project/xdp-project/blob/master/areas/core/xdp-multi-buffer01-design.org The use-case that really convinced me was Eric's packet header-split. Lets refresh: Why XDP don't have multi-buffer support: XDP is designed for maximum performance, which is why certain driver-level use-cases were not supported, like multi-buffer packets (like jumbo-frames). As it e.g. complicated the driver RX-loop and memory model handling. The single buffer per packet design, is also tied into eBPF Direct-Access (DA) to packet data, which can only be allowed if the packet memory is in contiguous memory. This DA feature is essential for XDP performance. One way forward is to define that XDP only get access to the first packet buffer, and it cannot see subsequent buffers. For XDP_TX and XDP_REDIRECT to work then XDP still need to carry pointers (plus len+offset) to the other buffers, which is 16 bytes per extra buffer. > [1] http://vger.kernel.org/netconf2019.html -- Best regards, Jesper Dangaard Brouer MSc.CS, Principal Kernel Engineer at Red Hat LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply index Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-23 7:06 [RFC V1 net-next 0/1] Introduce xdp to ena sameehj 2019-06-23 7:06 ` [RFC V1 net-next 1/1] net: ena: implement XDP drop support sameehj 2019-06-23 14:09 ` Jesper Dangaard Brouer 2019-06-23 14:21 ` Jesper Dangaard Brouer 2019-06-25 3:19 ` Machulsky, Zorik 2019-06-26 8:38 ` Jesper Dangaard Brouer [this message] 2019-06-26 11:52 ` XDP multi-buffer incl. jumbo-frames (Was: [RFC V1 net-next 1/1] net: ena: implement XDP drop support) Toke Høiland-Jørgensen 2019-06-26 14:40 ` Jesper Dangaard Brouer 2019-06-26 15:01 ` Toke Høiland-Jørgensen 2019-06-26 15:20 ` Willem de Bruijn 2019-06-26 16:42 ` Jonathan Lemon 2019-06-26 20:00 ` Jesper Dangaard Brouer 2019-06-27 22:07 ` Jonathan Lemon 2019-06-28 8:46 ` Jesper Dangaard Brouer 2019-06-26 15:14 ` Toke Høiland-Jørgensen 2019-06-26 16:36 ` Jesper Dangaard Brouer 2019-06-28 7:14 ` Eelco Chaudron 2019-06-28 7:46 ` Toke Høiland-Jørgensen 2019-06-28 11:49 ` Eelco Chaudron 2019-06-28 8:22 ` Jesper Dangaard Brouer 2019-06-23 14:28 ` [RFC V1 net-next 1/1] net: ena: implement XDP drop support David Ahern 2019-06-23 14:51 ` Maciej Fijalkowski
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190626103829.5360ef2d@carbon \ --to=brouer@redhat.com \ --cc=akiyano@amazon.com \ --cc=alexei.starovoitov@gmail.com \ --cc=aliguori@amazon.com \ --cc=alisaidi@amazon.com \ --cc=benh@amazon.com \ --cc=borkmann@iogearbox.net \ --cc=davem@davemloft.net \ --cc=dwmw@amazon.co.uk \ --cc=gtzalik@amazon.com \ --cc=ilias.apalodimas@linaro.org \ --cc=jakub.kicinski@netronome.com \ --cc=matua@amazon.com \ --cc=msw@amazon.com \ --cc=nafea@amazon.com \ --cc=netanel@amazon.com \ --cc=netdev@vger.kernel.org \ --cc=saeedb@amazon.com \ --cc=sameehj@amazon.com \ --cc=toke@redhat.com \ --cc=xdp-newbies@vger.kernel.org \ --cc=zorik@amazon.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Netdev Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/netdev/0 netdev/git/0.git git clone --mirror https://lore.kernel.org/netdev/1 netdev/git/1.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 netdev netdev/ https://lore.kernel.org/netdev \ netdev@vger.kernel.org public-inbox-index netdev Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.netdev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git