From: Alexander H Duyck <alexander.duyck@gmail.com>
To: Tirthendu Sarkar <tirthendu.sarkar@intel.com>,
tirtha@gmail.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, magnus.karlsson@intel.com
Subject: Re: [Intel-wired-lan] [PATCH intel-next 0/5] i40e: support XDP multi-buffer
Date: Tue, 13 Dec 2022 07:58:19 -0800 [thread overview]
Message-ID: <cf6f03d04c8f2ad2627a924f7ee66645d661d746.camel@gmail.com> (raw)
In-Reply-To: <20221213105023.196409-1-tirthendu.sarkar@intel.com>
On Tue, 2022-12-13 at 16:20 +0530, Tirthendu Sarkar wrote:
> This patchset adds multi-buffer support for XDP. The first four patches
> are prepatory patches while the fifth one contains actual multi-buffer
> changes.
>
> Tirthendu Sarkar (5):
> i40e: add pre-xdp page_count in rx_buffer
> i40e: avoid per buffer next_to_clean access from i40e_ring
> i40e: introduce next_to_process to i40e_ring
> i40e: pull out rx buffer allocation to end of i40e_clean_rx_irq()
> i40e: add support for XDP multi-buffer Rx
>
> drivers/net/ethernet/intel/i40e/i40e_main.c | 18 +-
> drivers/net/ethernet/intel/i40e/i40e_txrx.c | 378 ++++++++++++++------
> drivers/net/ethernet/intel/i40e/i40e_txrx.h | 13 +-
> 3 files changed, 280 insertions(+), 129 deletions(-)
>
This approach seems kind of convoluted to me. Basically you are trying
to clean the ring without cleaning the ring in the cases where you
encounter a non EOP descriptor.
Why not just replace the skb pointer with an xdp_buff in the ring? Then
you just build an xdp_buff w/ frags and then convert it after after
i40e_is_non_eop? You should then still be able to use all the same page
counting tricks and the pages would just be dropped into the shared
info of an xdp_buff instead of an skb and function the same assuming
you have all the logic in place to clean them up correctly.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-12-13 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 10:50 [Intel-wired-lan] [PATCH intel-next 0/5] i40e: support XDP multi-buffer Tirthendu Sarkar
2022-12-13 10:50 ` [Intel-wired-lan] [PATCH intel-next 1/5] i40e: add pre-xdp page_count in rx_buffer Tirthendu Sarkar
2022-12-13 10:50 ` [Intel-wired-lan] [PATCH intel-next 2/5] i40e: avoid per buffer next_to_clean access from i40e_ring Tirthendu Sarkar
2022-12-13 10:50 ` [Intel-wired-lan] [PATCH intel-next 3/5] i40e: introduce next_to_process to i40e_ring Tirthendu Sarkar
2022-12-13 10:50 ` [Intel-wired-lan] [PATCH intel-next 4/5] i40e: pull out rx buffer allocation to end of i40e_clean_rx_irq() Tirthendu Sarkar
2022-12-13 16:09 ` Alexander H Duyck
2022-12-13 10:50 ` [Intel-wired-lan] [PATCH intel-next 5/5] i40e: add support for XDP multi-buffer Rx Tirthendu Sarkar
2022-12-13 13:14 ` kernel test robot
2022-12-13 15:58 ` Alexander H Duyck [this message]
2022-12-14 15:56 ` [Intel-wired-lan] [PATCH intel-next 0/5] i40e: support XDP multi-buffer Sarkar, Tirthendu
2022-12-14 17:16 ` Alexander Duyck
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=cf6f03d04c8f2ad2627a924f7ee66645d661d746.camel@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tirtha@gmail.com \
--cc=tirthendu.sarkar@intel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox