On Thu, Apr 18, 2024 at 10:19:33PM +0200, Jesper Dangaard Brouer wrote:
> I'm not sure it is "fine" to, explicitly choosing not to use page pool,
> and then (ab)use `struct page` member (pp) that intended for page_pool
> for other stuff. (In this case create a linked list of pages).
>
> +#define page_chain_next(p) ((struct page *)((p)->pp))
> +#define page_chain_add(p, n) ((p)->pp = (void *)n)
>
> I'm not sure that I (as PP maintainer) can make this call actually, as I
> think this area belong with the MM "page" maintainers (Cc MM-list +
> people) to judge.
>
> Just invention new ways to use struct page fields without adding your
> use-case to struct page, will make it harder for MM people to maintain
> (e.g. make future change).
I can't really follow what's being proposed; the quoting is quite deep.
Here's the current plan for struct page:
- The individual users are being split off. This has already happened
for struct folio, struct slab and struct pgdesc. Others are hopefully
coming.
- At some point, struct page will become:
struct page {
unsigned long flags;
unsigned long data[5];
unsigned int data2[2];
... some other bits and pieces ...
};
- After that, we will turn struct page into:
struct page {
unsigned long memdesc;
};
Users like pagepool will allocate a struct ppdesc that will be
referred to by the memdesc. The bottom 4 bits will identify it as a
ppdesc. You can put anything you like in a struct ppdesc, it just has
to be allocated from a slab with a 16 byte alignment.
More details here:
https://kernelnewbies.org/MatthewWilcox/Memdescs
This is all likely to land in 2025. The goal for 2024 is to remove
mapping & index from 'struct page'. This has been in progress since
2019 so I'm really excited that we're so close! If you want to
turn struct ppdesc into its own struct like folio, slab & ptdesc,
I'm happy to help. I once had a patchset for that:
https://lore.kernel.org/netdev/20221130220803.3657490-1-willy@xxxxxxxxxxxxx/
but I'm sure it's truly bitrotted.
