From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Liang Chen <liangchen.linux@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, hawk@kernel.org, linyunsheng@huawei.com,
netdev@vger.kernel.org, linux-mm@kvack.org, jasowang@redhat.com
Subject: Re: [PATCH net-next v6 3/4] skbuff: Add a function to check if a page belongs to page_pool
Date: Tue, 5 Dec 2023 13:02:46 +0200 [thread overview]
Message-ID: <CAC_iWj+8srOuAxEMe5rt7vk1d=6V2ZDzjsHameaSt0a+rxwdhA@mail.gmail.com> (raw)
In-Reply-To: <CAKhg4t+hBgmEnZ6d+GKBRN7+wCqHVrOhEaaTAUViME_Mmu1K5w@mail.gmail.com>
Hi Liang,
On Mon, 4 Dec 2023 at 04:40, Liang Chen <liangchen.linux@gmail.com> wrote:
>
> On Fri, Dec 1, 2023 at 6:23 PM Ilias Apalodimas
> <ilias.apalodimas@linaro.org> wrote:
> >
> > The second time is the charm, apologize for the noise.. resending it
> > as plain-text
> >
> > On Thu, 30 Nov 2023 at 13:59, Liang Chen <liangchen.linux@gmail.com> wrote:
> > >
> > > Wrap code for checking if a page is a page_pool page into a
> > > function for better readability and ease of reuse.
> > >
> > > Signed-off-by: Liang Chen <liangchen.linux@gmail.com>
> > > Reviewed-by: Yunsheng Lin <linyunsheng@huawei.com>
> > > ---
> > > net/core/skbuff.c | 7 ++++++-
> > > 1 file changed, 6 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> > > index b157efea5dea..31e57c29c556 100644
> > > --- a/net/core/skbuff.c
> > > +++ b/net/core/skbuff.c
> > > @@ -890,6 +890,11 @@ static void skb_clone_fraglist(struct sk_buff *skb)
> > > skb_get(list);
> > > }
> > >
> > > +static bool skb_frag_is_pp_page(struct page *page)
> > > +{
> > > + return (page->pp_magic & ~0x3UL) == PP_SIGNATURE;
> > > +}
> > > +
> >
> > That's fine, but why _frag? The same logic applies to non-fragmented pages no?
> > So rename it to skb_from_pp()?
> >
>
> Yeah, the same logic applies to non-fragmented pages. How about
> changing it to 'is_pp_page'? It takes a page as an argument instead of
> the entire skb.
Naming stuff is always hard. Any of skb_from_pp/is_pp_page would work for me
Thanks
/Ilias
> > [...]
> >
> > Thanks
> > /Ilias
next prev parent reply other threads:[~2023-12-05 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 11:56 [PATCH net-next v6 0/4] skbuff: Optimize SKB coalescing for page pool Liang Chen
2023-11-30 11:56 ` [PATCH net-next v6 1/4] page_pool: Rename pp_frag_count to pp_ref_count Liang Chen
[not found] ` <CAC_iWjL68n-GRN7vs_jwvzbnVy8sPh4_SP=wVDq0HkFOmSU-nQ@mail.gmail.com>
2023-12-01 10:10 ` Ilias Apalodimas
2023-12-02 2:19 ` Jakub Kicinski
2023-12-04 2:39 ` Liang Chen
2023-11-30 11:56 ` [PATCH net-next v6 2/4] page_pool: halve BIAS_MAX for multiple user references of a fragment Liang Chen
2023-11-30 11:56 ` [PATCH net-next v6 3/4] skbuff: Add a function to check if a page belongs to page_pool Liang Chen
2023-12-01 10:22 ` Ilias Apalodimas
2023-12-04 2:40 ` Liang Chen
2023-12-05 11:02 ` Ilias Apalodimas [this message]
2023-11-30 11:56 ` [PATCH net-next v6 4/4] skbuff: Optimization of SKB coalescing for page pool Liang Chen
2023-12-01 10:34 ` Ilias Apalodimas
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='CAC_iWj+8srOuAxEMe5rt7vk1d=6V2ZDzjsHameaSt0a+rxwdhA@mail.gmail.com' \
--to=ilias.apalodimas@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=liangchen.linux@gmail.com \
--cc=linux-mm@kvack.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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).