From: sashiko-bot@kernel.org
To: "Mina Almasry" <almasrymina@google.com>
Cc: virtualization@lists.linux.dev, linux-rdma@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH net-next v2 4/5] net: remove skb->pp_recycle and consolidate netmem refcounting
Date: Mon, 09 Nov 2026 06:00:42 +0000 [thread overview]
Message-ID: <sashiko-outbox-204473@kernel.org> (raw)
In-Reply-To: <20261108060016.2131509-5-almasrymina@google.com>
> skb->pp_recycle was introduced in commit 6a5bcd84e886 ("page_pool: Allow
> drivers to hint on SKB recycling") when drivers had to explicitly opt in
> to page_pool SKB recycling and to avoid touching struct page on the free
> path. Today every page_pool-backed netmem carries its own identity via
> netmem_is_pp(), making the per-SKB skb->pp_recycle bitfield redundant
> and error-prone when SKBs are cloned, split, segmented, shifted, or
> coalesced across page_pool and non-page_pool buffers. For non-page_pool
> pages, get_page(), put_page(), and skb_free_frag() immediately load the
> same first struct page cache line (compound_head, which shares the cache
> line with pp_magic), so checking netmem_is_pp() does not add an extra
> cache-line load.
>
> Remove skb->pp_recycle and check netmem_is_pp() directly via
> napi_pp_get_page() and napi_pp_put_page() inside netmem_inc_ref(),
> netmem_dec_ref(), and skb_pp_recycle(), dropping the now-redundant
> [ ... ]
> skb_irq_freeable() does not exclude SKBs holding page_pool memory
> before calling __kfree_skb() with hardirqs disabled; TX SKBs carrying
> spliced page_pool fragments are subject to the same path.
>
> Signed-off-by: Mina Almasry <almasrymina@google.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261108060016.2131509-1-almasrymina@google.com?part=4
next prev parent reply other threads:[~2026-11-09 6:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 6:00 [PATCH net-next v2 0/5] net: deprecate skb->pp_recycle and skb_mark_for_recycle() Mina Almasry
2026-11-08 6:00 ` [PATCH net-next v2 1/5] net: skbuff: skip managed zerocopy frags in skb_frag_ref() Mina Almasry
2026-11-09 6:00 ` sashiko-bot
2026-11-08 6:00 ` [PATCH net-next v2 2/5] net: skbuff: refcount spliced page_pool frags via skb_pipe_buf_ops Mina Almasry
2026-11-09 6:00 ` sashiko-bot
2026-11-08 6:00 ` [PATCH net-next v2 3/5] tcp: detach page_pool pages before mapping in tcp_zerocopy_receive() Mina Almasry
2026-11-09 6:00 ` sashiko-bot
2026-11-08 6:00 ` [PATCH net-next v2 4/5] net: remove skb->pp_recycle and consolidate netmem refcounting Mina Almasry
2026-11-09 6:00 ` sashiko-bot [this message]
2026-11-08 6:00 ` [PATCH net-next v2 5/5] net: remove skb_mark_for_recycle() Mina Almasry
2026-11-09 6:00 ` sashiko-bot
2026-11-11 1:13 ` [PATCH net-next v2 0/5] net: deprecate skb->pp_recycle and skb_mark_for_recycle() Jakub Kicinski
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=sashiko-outbox-204473@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=almasrymina@google.com \
--cc=eperezma@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
/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