From: Liang Chen <liangchen.linux@gmail.com>
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, hawk@kernel.org, ilias.apalodimas@linaro.org,
netdev@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH net-next v4 3/4] skbuff: Add a function to check if a page belongs to page_pool
Date: Wed, 29 Nov 2023 15:08:24 +0800 [thread overview]
Message-ID: <CAKhg4tJ4vFpsO+=JMCboan==JsKhEjGDVeBk=cM+BmVO+xqFNg@mail.gmail.com> (raw)
In-Reply-To: <844dc02a-3559-5a53-943d-28f772670879@huawei.com>
On Wed, Nov 29, 2023 at 11:40 AM Yunsheng Lin <linyunsheng@huawei.com> wrote:
>
> On 2023/11/29 11:12, Liang Chen 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>
> > ---
> > 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..310207389f51 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 inline bool skb_frag_is_pp_page(struct page *page)
>
> I am not sure about the 'skb_frag' part, But I am not able to come
> up with a better name too:)
>
So, let's leave it there for now:)
> Also, Generally, 'inline' is not really encouraged in c file in
> the networking unless there is a clear justification as the compiler
> can make better decision about whether inlining most of the time.
>
Sure. will remove 'inline' in v5.
> Other than the 'inlining' part, LGTM.
> Reviewed-by: Yunsheng Lin <linyunsheng@huawei.com>
>
> > +{
> > + return (page->pp_magic & ~0x3UL) == PP_SIGNATURE;
> > +}
> > +
> > #if IS_ENABLED(CONFIG_PAGE_POOL)
> > bool napi_pp_put_page(struct page *page, bool napi_safe)
> > {
> > @@ -905,7 +910,7 @@ bool napi_pp_put_page(struct page *page, bool napi_safe)
> > * and page_is_pfmemalloc() is checked in __page_pool_put_page()
> > * to avoid recycling the pfmemalloc page.
> > */
> > - if (unlikely((page->pp_magic & ~0x3UL) != PP_SIGNATURE))
> > + if (unlikely(!skb_frag_is_pp_page(page)))
> > return false;
> >
> > pp = page->pp;
> >
next prev parent reply other threads:[~2023-11-29 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 3:11 [PATCH net-next v4 0/4] skbuff: Optimize SKB coalescing for page pool Liang Chen
2023-11-29 3:11 ` [PATCH net-next v4 1/4] page_pool: Rename pp_frag_count to pp_ref_count Liang Chen
2023-11-29 3:30 ` Yunsheng Lin
2023-11-29 3:11 ` [PATCH net-next v4 2/4] page_pool: halve BIAS_MAX for multiple user references of a fragment Liang Chen
2023-11-29 3:12 ` [PATCH net-next v4 3/4] skbuff: Add a function to check if a page belongs to page_pool Liang Chen
2023-11-29 3:40 ` Yunsheng Lin
2023-11-29 7:08 ` Liang Chen [this message]
2023-11-29 3:12 ` [PATCH net-next v4 4/4] skbuff: Optimization of SKB coalescing for page pool Liang Chen
2023-11-29 3:56 ` Yunsheng Lin
2023-11-29 7:08 ` Liang Chen
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='CAKhg4tJ4vFpsO+=JMCboan==JsKhEjGDVeBk=cM+BmVO+xqFNg@mail.gmail.com' \
--to=liangchen.linux@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--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