mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <hawk@kernel.org>
To: Mina Almasry <almasrymina@google.com>,
	netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@kernel.org>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"John Fastabend" <john.fastabend@gmail.com>,
	"Stanislav Fomichev" <sdf@fomichev.me>,
	"Luigi Rizzo" <lrizzo@google.com>,
	"Björn Töpel" <bjorn@kernel.org>,
	"Pavel Begunkov" <asml.silence@gmail.com>
Subject: Re: [PATCH net-next v1 1/2] net: netmem: document netmem and memory provider design in comments
Date: Wed, 7 Oct 2026 09:43:49 +0200	[thread overview]
Message-ID: <4818da7c-be7e-4f97-b5a3-bee05ada500a@kernel.org> (raw)
In-Reply-To: <20261005004958.3603059-2-almasrymina@google.com>



On 10/5/26 02:49, Mina Almasry wrote:
> Clarify the netmem, memory provider, page_pool, and skb fragment design
> principles in header and code comments:
> 
> - Memory providers allocate struct net_iov or struct page, cast them to
>    netmem_ref, and pass them to page_pool; page_pool, drivers, and the
>    core stack operate on netmem_ref and must not downcast to page or
>    net_iov outside dedicated netmem helpers.
> - Memory providers are not restricted to net_iov and may supply
>    page-backed netmems.
> - net_iov is not inherently unreadable; future readable net_iov types
>    are allowed.
> - Per-provider logic belongs in memory_provider_ops, and per-netmem-type
>    logic belongs in netmem helpers.
> - All frags in an skb must share the same backing netmem memory type,
>    and skbs with different frag memory types must not be coalesced.
> 
> Cc: Luigi Rizzo <lrizzo@google.com>
> Cc: Björn Töpel <bjorn@kernel.org>
> Cc: Stanislav Fomichev <sdf@fomichev.me>
> Cc: Pavel Begunkov <asml.silence@gmail.com>
> Signed-off-by: Mina Almasry <almasrymina@google.com>
> ---
>   include/linux/skbuff.h                  |  4 ++++
>   include/net/netmem.h                    | 29 ++++++++++++++++---------

./scripts/get_maintainer.pl --file include/net/netmem.h

Returns "maintainer:NETWORKING [GENERAL]"

>   include/net/page_pool/helpers.h         | 18 ++++++++++-----
>   include/net/page_pool/memory_provider.h |  8 +++++++
>   include/net/page_pool/types.h           |  6 ++---
>   net/core/skbuff.c                       |  3 +++
>   6 files changed, 50 insertions(+), 18 deletions(-)

Changes LGTM.

I suggest that you Mina is added the MAINTAINERS for PAGE POOL.
And do we want a new section for NETMEM ?

Acked-by: Jesper Dangaard Brouer <hawk@kernel.org>


  reply	other threads:[~2026-10-07  7:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05  0:49 [PATCH net-next v1 0/2] net: netmem: document design principles and intended direction Mina Almasry
2026-10-05  0:49 ` [PATCH net-next v1 1/2] net: netmem: document netmem and memory provider design in comments Mina Almasry
2026-10-07  7:43   ` Jesper Dangaard Brouer [this message]
2026-10-05  0:49 ` [PATCH net-next v1 2/2] docs: netmem: document netmem and memory provider design principles Mina Almasry
2026-10-05 16:19   ` Stanislav Fomichev
2026-10-05 16:31     ` Mina Almasry
2026-10-06 22:02       ` Stanislav Fomichev

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=4818da7c-be7e-4f97-b5a3-bee05ada500a@kernel.org \
    --to=hawk@kernel.org \
    --cc=almasrymina@google.com \
    --cc=asml.silence@gmail.com \
    --cc=ast@kernel.org \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrizzo@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=sdf@fomichev.me \
    --cc=skhan@linuxfoundation.org \
    /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

all inboxes | Powered by JetHome®