From: Byungchul Park <byungchul@sk.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, kernel_team@skhynix.com, kuba@kernel.org,
almasrymina@google.com, ilias.apalodimas@linaro.org,
harry.yoo@oracle.com, hawk@kernel.org, akpm@linux-foundation.org,
ast@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
john.fastabend@gmail.com, andrew+netdev@lunn.ch,
edumazet@google.com, pabeni@redhat.com, vishal.moola@gmail.com
Subject: Re: [RFC 19/19] mm, netmem: remove the page pool members in struct page
Date: Mon, 12 May 2025 21:51:03 +0900 [thread overview]
Message-ID: <20250512125103.GC45370@system.software.com> (raw)
In-Reply-To: <aB5DNqwP_LFV_ULL@casper.infradead.org>
On Fri, May 09, 2025 at 07:02:30PM +0100, Matthew Wilcox wrote:
> On Fri, May 09, 2025 at 08:51:26PM +0900, Byungchul Park wrote:
> > +++ b/include/linux/mm_types.h
> > @@ -20,6 +20,7 @@
> > #include <linux/seqlock.h>
> > #include <linux/percpu_counter.h>
> > #include <linux/types.h>
> > +#include <net/netmem_type.h> /* for page pool */
> >
> > #include <asm/mmu.h>
> >
> > @@ -118,17 +119,7 @@ struct page {
> > */
> > unsigned long private;
> > };
> > - struct { /* page_pool used by netstack */
> > - /**
> > - * @pp_magic: magic value to avoid recycling non
> > - * page_pool allocated pages.
> > - */
> > - unsigned long pp_magic;
> > - struct page_pool *pp;
> > - unsigned long _pp_mapping_pad;
> > - unsigned long dma_addr;
> > - atomic_long_t pp_ref_count;
> > - };
> > + struct __netmem_desc place_holder_1; /* for page pool */
> > struct { /* Tail pages of compound page */
> > unsigned long compound_head; /* Bit zero is set */
> > };
>
> The include and the place holder aren't needed.
Or netmem_desc overlaying struct page might be conflict with other
fields of sturct page e.g. _mapcount, _refcount and the like, once the
layout of struct page *extremly changes* in the future before
netmem_desc has its own instance.
So placing a place holder like this is the safest way, IMO, to prevent
the unextected result. Am I missing something?
> > diff --git a/include/net/netmem.h b/include/net/netmem.h
> > index 00064e766b889..c414de6c6ab0d 100644
> > --- a/include/net/netmem.h
> > +++ b/include/net/netmem.h
> > @@ -10,6 +10,7 @@
> >
> > #include <linux/mm.h>
> > #include <net/net_debug.h>
> > +#include <net/netmem_type.h>
>
> ... which I think means you don't need the separate header file.
Agree if I don't use the place holder in mm_types.h.
> > /* net_iov */
> >
> > @@ -20,15 +21,6 @@ DECLARE_STATIC_KEY_FALSE(page_pool_mem_providers);
> > */
> > #define NET_IOV 0x01UL
> >
> > -struct netmem_desc {
> > - unsigned long __unused_padding;
> > - unsigned long pp_magic;
> > - struct page_pool *pp;
> > - struct net_iov_area *owner;
> > - unsigned long dma_addr;
> > - atomic_long_t pp_ref_count;
> > -};
> > -
> > struct net_iov_area {
> > /* Array of net_iovs for this area. */
> > struct netmem_desc *niovs;
> > @@ -38,31 +30,6 @@ struct net_iov_area {
> > unsigned long base_virtual;
> > };
> >
> > -/* These fields in struct page are used by the page_pool and net stack:
> > - *
> > - * struct {
> > - * unsigned long pp_magic;
> > - * struct page_pool *pp;
> > - * unsigned long _pp_mapping_pad;
> > - * unsigned long dma_addr;
> > - * atomic_long_t pp_ref_count;
> > - * };
> > - *
> > - * We mirror the page_pool fields here so the page_pool can access these fields
> > - * without worrying whether the underlying fields belong to a page or net_iov.
> > - *
> > - * The non-net stack fields of struct page are private to the mm stack and must
> > - * never be mirrored to net_iov.
> > - */
> > -#define NET_IOV_ASSERT_OFFSET(pg, iov) \
> > - static_assert(offsetof(struct page, pg) == \
> > - offsetof(struct netmem_desc, iov))
> > -NET_IOV_ASSERT_OFFSET(pp_magic, pp_magic);
> > -NET_IOV_ASSERT_OFFSET(pp, pp);
> > -NET_IOV_ASSERT_OFFSET(dma_addr, dma_addr);
> > -NET_IOV_ASSERT_OFFSET(pp_ref_count, pp_ref_count);
> > -#undef NET_IOV_ASSERT_OFFSET
>
> ... but you do want to keep asserting that netmem_desc and
> net_iov have the same offsets. And you want to assert that struct page
> is big enough to hold everything in netmem_desc, like we do for slab:
>
> static_assert(sizeof(struct slab) <= sizeof(struct page));
I will. However, as I mentioned above, the total size doesn't matter
but the layout change of struct page might matter, I think.
Byungchul
next prev parent reply other threads:[~2025-05-12 12:51 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 11:51 [RFC 00/19] Split netmem from " Byungchul Park
2025-05-09 11:51 ` [RFC 01/19] netmem: rename struct net_iov to struct netmem_desc Byungchul Park
2025-05-12 13:11 ` Pavel Begunkov
2025-05-12 13:29 ` Byungchul Park
2025-05-12 19:14 ` Mina Almasry
2025-05-13 2:00 ` Byungchul Park
2025-05-13 12:58 ` Pavel Begunkov
2025-05-13 12:49 ` Pavel Begunkov
2025-05-14 0:07 ` Byungchul Park
2025-05-09 11:51 ` [RFC 02/19] netmem: introduce netmem alloc/put API to wrap page alloc/put API Byungchul Park
2025-05-09 13:39 ` Mina Almasry
2025-05-09 14:08 ` Mina Almasry
2025-05-12 12:30 ` Byungchul Park
2025-05-09 11:51 ` [RFC 03/19] page_pool: use netmem alloc/put API in __page_pool_alloc_page_order() Byungchul Park
2025-05-09 11:51 ` [RFC 04/19] page_pool: rename __page_pool_alloc_page_order() to __page_pool_alloc_large_netmem() Byungchul Park
2025-05-09 11:51 ` [RFC 05/19] page_pool: use netmem alloc/put API in __page_pool_alloc_pages_slow() Byungchul Park
2025-05-09 11:51 ` [RFC 06/19] page_pool: rename page_pool_return_page() to page_pool_return_netmem() Byungchul Park
2025-05-09 11:51 ` [RFC 07/19] page_pool: use netmem alloc/put API in page_pool_return_netmem() Byungchul Park
2025-05-09 11:51 ` [RFC 08/19] page_pool: rename __page_pool_release_page_dma() to __page_pool_release_netmem_dma() Byungchul Park
2025-05-09 11:51 ` [RFC 09/19] page_pool: rename __page_pool_put_page() to __page_pool_put_netmem() Byungchul Park
2025-05-09 11:51 ` [RFC 10/19] page_pool: rename __page_pool_alloc_pages_slow() to __page_pool_alloc_netmems_slow() Byungchul Park
2025-05-09 11:51 ` [RFC 11/19] mlx4: use netmem descriptor and API for page pool Byungchul Park
2025-05-09 11:51 ` [RFC 12/19] netmem: introduce page_pool_recycle_direct_netmem() Byungchul Park
2025-05-09 11:51 ` [RFC 13/19] page_pool: expand scope of is_pp_{netmem,page}() to global Byungchul Park
2025-05-12 12:46 ` Toke Høiland-Jørgensen
2025-05-12 12:55 ` Byungchul Park
2025-05-14 3:00 ` Byungchul Park
2025-05-14 11:17 ` Toke Høiland-Jørgensen
2025-05-09 11:51 ` [RFC 14/19] mm: page_alloc: do not directly access page->pp_magic but use is_pp_page() Byungchul Park
2025-05-09 11:51 ` [RFC 15/19] mlx5: use netmem descriptor and API for page pool Byungchul Park
2025-05-09 11:51 ` [RFC 16/19] netmem: use _Generic to cover const casting for page_to_netmem() Byungchul Park
2025-05-09 11:51 ` [RFC 17/19] netmem: remove __netmem_get_pp() Byungchul Park
2025-05-09 13:47 ` Mina Almasry
2025-05-09 11:51 ` [RFC 18/19] page_pool: make page_pool_get_dma_addr() just wrap page_pool_get_dma_addr_netmem() Byungchul Park
2025-05-09 13:49 ` Mina Almasry
2025-05-10 7:28 ` Ilias Apalodimas
2025-05-09 11:51 ` [RFC 19/19] mm, netmem: remove the page pool members in struct page Byungchul Park
2025-05-09 17:32 ` Mina Almasry
2025-05-09 18:11 ` Matthew Wilcox
2025-05-09 19:04 ` Mina Almasry
2025-05-09 19:48 ` Matthew Wilcox
2025-05-12 19:10 ` Mina Almasry
2025-05-09 18:02 ` Matthew Wilcox
2025-05-12 12:51 ` Byungchul Park [this message]
2025-05-12 14:42 ` Matthew Wilcox
2025-05-13 1:42 ` Byungchul Park
2025-05-13 3:19 ` Matthew Wilcox
2025-05-13 10:24 ` Byungchul Park
2025-05-10 7:26 ` Ilias Apalodimas
2025-05-12 12:58 ` Byungchul Park
2025-05-09 14:09 ` [RFC 00/19] Split netmem from " Mina Almasry
2025-05-12 12:36 ` Byungchul Park
2025-05-12 12:59 ` Pavel Begunkov
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=20250512125103.GC45370@system.software.com \
--to=byungchul@sk.com \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=harry.yoo@oracle.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kernel_team@skhynix.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vishal.moola@gmail.com \
--cc=willy@infradead.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