From: Mina Almasry <almasrymina@google.com>
To: Liang Chen <liangchen.linux@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, hawk@kernel.org, ilias.apalodimas@linaro.org,
linyunsheng@huawei.com, netdev@vger.kernel.org,
linux-mm@kvack.org, jasowang@redhat.com
Subject: Re: [PATCH net-next v9 3/4] skbuff: Add a function to check if a page belongs to page_pool
Date: Tue, 12 Dec 2023 17:50:51 -0800 [thread overview]
Message-ID: <CAHS8izOk79ajSuZ=-Ca1br12H39vG6YXnHJnd5p6CDCFJz1vTg@mail.gmail.com> (raw)
In-Reply-To: <20231212044614.42733-4-liangchen.linux@gmail.com>
On Mon, Dec 11, 2023 at 8:47 PM 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>
> Reviewed-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Only 1 nit, feel free to ignore since especially if Jakub wants to
merge the patch asap.
Reviewed-by: Mina Almasry <almasrymina@google.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..7e26b56cda38 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 is_pp_page(struct page *page)
> +{
> + 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(!is_pp_page(page)))
Nit: I think the unlikely here is unnecessary anyway, and can be
removed (if without else is already unlikely).
> return false;
>
> pp = page->pp;
> --
> 2.31.1
>
>
--
Thanks,
Mina
next prev parent reply other threads:[~2023-12-13 1:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 4:46 [PATCH net-next v9 0/4] skbuff: Optimize SKB coalescing for page pool Liang Chen
2023-12-12 4:46 ` [PATCH net-next v9 1/4] page_pool: transition to reference count management after page draining Liang Chen
2023-12-13 1:53 ` Mina Almasry
2023-12-12 4:46 ` [PATCH net-next v9 2/4] page_pool: halve BIAS_MAX for multiple user references of a fragment Liang Chen
2023-12-13 1:51 ` Mina Almasry
2023-12-13 11:38 ` Ilias Apalodimas
2023-12-14 3:42 ` Liang Chen
2023-12-12 4:46 ` [PATCH net-next v9 3/4] skbuff: Add a function to check if a page belongs to page_pool Liang Chen
2023-12-13 1:50 ` Mina Almasry [this message]
2023-12-12 4:46 ` [PATCH net-next v9 4/4] skbuff: Optimization of SKB coalescing for page pool Liang Chen
2023-12-13 1:49 ` Mina Almasry
2023-12-13 2:37 ` Liang Chen
2023-12-13 2:49 ` Mina Almasry
2023-12-14 3:00 ` [PATCH net-next v9 0/4] skbuff: Optimize " patchwork-bot+netdevbpf
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='CAHS8izOk79ajSuZ=-Ca1br12H39vG6YXnHJnd5p6CDCFJz1vTg@mail.gmail.com' \
--to=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.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