From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, claudiu.manoil@nxp.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, lorenzo.bianconi@redhat.com
Subject: Re: [PATCH net-next] net: ethernet: enetc: set frag flag for non-linear xdp buffers
Date: Tue, 6 Dec 2022 14:30:41 +0100 [thread overview]
Message-ID: <Y49EARwosUGZfvcL@lore-desk> (raw)
In-Reply-To: <20221206123552.6yqwxg3tlakgnkmf@skbuf>
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
> Hi Lorenzo,
Hi Vladimir,
>
> On Sun, Dec 04, 2022 at 11:33:23PM +0100, Lorenzo Bianconi wrote:
> > Set missing XDP_FLAGS_HAS_FRAGS bit in enetc_add_rx_buff_to_xdp for
> > non-linear xdp buffers.
> >
> > Fixes: d1b15102dd16 ("net: enetc: add support for XDP_DROP and XDP_PASS")
>
> This can't be the Fixes: tag, struct xdp_buff didn't even have a "flags"
> field when that commit was introduced.
yes, my fault, I did not check dates, I assumed this commit was done after xdp
multi-buff support. We should get rid of the Fixes tag.
>
> Also, what does this change aim to achieve? It has a Fixes: tag but it's
> aimed for net-next. Is it to enable multi-buff XDP support? But we also
> have this in place, shouldn't that be deleted too?
I think we should get rid of the chunk below as well. I am currently working on
xdp feature support in order to allow XDP_REDIRECT for S/G xdp frames.
I will post a v2.
Regards,
Lorenzo
>
> case XDP_REDIRECT:
> /* xdp_return_frame does not support S/G in the sense
> * that it leaks the fragments (__xdp_return should not
> * call page_frag_free only for the initial buffer).
> * Until XDP_REDIRECT gains support for S/G let's keep
> * the code structure in place, but dead. We drop the
> * S/G frames ourselves to avoid memory leaks which
> * would otherwise leave the kernel OOM.
> */
> if (unlikely(cleaned_cnt - orig_cleaned_cnt != 1)) {
> enetc_xdp_drop(rx_ring, orig_i, i);
> rx_ring->stats.xdp_redirect_sg++;
> break;
> }
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2022-12-06 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 22:33 [PATCH net-next] net: ethernet: enetc: set frag flag for non-linear xdp buffers Lorenzo Bianconi
2022-12-06 12:35 ` Vladimir Oltean
2022-12-06 13:30 ` Lorenzo Bianconi [this message]
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=Y49EARwosUGZfvcL@lore-desk \
--to=lorenzo@kernel.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.