From: Byungchul Park <byungchul@sk.com>
To: Mina Almasry <almasrymina@google.com>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
axboe@kernel.dk, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
hawk@kernel.org, ilias.apalodimas@linaro.org, sdf@fomichev.me,
dw@davidwei.uk, ap420073@gmail.com, dtatulea@nvidia.com,
toke@redhat.com, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
kernel_team@skhynix.com, max.byungchul.park@gmail.com
Subject: Re: [PATCH net-next] page_pool: check if nmdesc->pp is !NULL to confirm its usage as pp for net_iov
Date: Sat, 18 Oct 2025 13:46:53 +0900 [thread overview]
Message-ID: <20251018044653.GA66683@system.software.com> (raw)
In-Reply-To: <CAHS8izMdwiijk_15NgecSOi_VD3M7cx5M0XLAWxQqWnZgJksjg@mail.gmail.com>
On Fri, Oct 17, 2025 at 08:13:14AM -0700, Mina Almasry wrote:
> On Fri, Oct 17, 2025 at 5:32 AM Pavel Begunkov <asml.silence@gmail.com> wrote:
> >
> > On 10/16/25 08:21, Byungchul Park wrote:
> > > On Thu, Oct 16, 2025 at 03:36:57PM +0900, Byungchul Park wrote:
> > >> ->pp_magic field in struct page is current used to identify if a page
> > >> belongs to a page pool. However, ->pp_magic will be removed and page
> > >> type bit in struct page e.g. PGTY_netpp should be used for that purpose.
> > >>
> > >> As a preparation, the check for net_iov, that is not page-backed, should
> > >> avoid using ->pp_magic since net_iov doens't have to do with page type.
> > >> Instead, nmdesc->pp can be used if a net_iov or its nmdesc belongs to a
> > >> page pool, by making sure nmdesc->pp is NULL otherwise.
> > >>
> > >> For page-backed netmem, just leave unchanged as is, while for net_iov,
> > >> make sure nmdesc->pp is initialized to NULL and use nmdesc->pp for the
> > >> check.
> > >
> > > IIRC,
> > >
> > > Suggested-by: Pavel Begunkov <asml.silence@gmail.com>
> >
> > Pointing out a problem in a patch with a fix doesn't qualify to
> > me as "suggested-by", you don't need to worry about that.
> >
> > Did you get the PGTY bits merged? There is some uneasiness about
> > this patch as it does nothing good by itself, it'd be much better
> > to have it in a series finalising the page_pool conversion. And
> > I don't think it simplify merging anyhow, hmm?
> >
>
> +1 honestly.
>
> If you want to 'extract the networking bits' into its own patch, let
> it be a patch series where this is a patch doing pre-work, and the
> next patches in the series are adding the page_flag.
Okay. Then is it possible that one for mm tree and the other for
net-next in the same patch series? I've never tried patches that way.
> I don't want added netmem_is_net_iov checks unnecessarily tbh. These
> checks are bad and only used when absolutely necessary, so let the
> patch series that adds them also do something useful (i.e. add the
> page flag), if possible. But I honestly think this patch was almost
> good as-is:
Hm.. but the following patch includes both networking changes and mm
changes. Jakub thinks it should go to mm and I don't know how Andrew
thinks it should be. It's not clear even to me.
That's why I splitted it into two, and this is the networking part, and
I will post the mm part to mm folks later. Any suggestions?
Byungchul
> https://lore.kernel.org/all/20250729110210.48313-1-byungchul@sk.com/
>
> You just need to address Jakub's review comments and resubmit? Not
> sure why we want to split, but if you want let it be a patch series
> that does something useful.
>
> --
> Thanks,
> Mina
next prev parent reply other threads:[~2025-10-18 4:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 6:36 [PATCH net-next] page_pool: check if nmdesc->pp is !NULL to confirm its usage as pp for net_iov Byungchul Park
2025-10-16 7:21 ` Byungchul Park
2025-10-17 12:33 ` Pavel Begunkov
2025-10-17 15:13 ` Mina Almasry
2025-10-18 4:46 ` Byungchul Park [this message]
2025-10-18 15:05 ` Mina Almasry
2025-10-23 8:27 ` Byungchul Park
2025-10-16 23:31 ` Byungchul Park
2025-10-17 6:26 ` Byungchul Park
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=20251018044653.GA66683@system.software.com \
--to=byungchul@sk.com \
--cc=almasrymina@google.com \
--cc=ap420073@gmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=io-uring@vger.kernel.org \
--cc=kernel_team@skhynix.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max.byungchul.park@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=toke@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).