From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Larysa Zaremba <larysa.zaremba@intel.com>,
Alexander Duyck <alexanderduyck@fb.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
Simon Horman <simon.horman@corigine.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 2/9] net: skbuff: don't include <net/page_pool/types.h> to <linux/skbuff.h>
Date: Tue, 1 Aug 2023 15:25:38 +0200 [thread overview]
Message-ID: <61965a16-55bf-2f81-8938-856f834d35bf@intel.com> (raw)
In-Reply-To: <5830338c-d025-2fb8-46a6-58508493b2cf@huawei.com>
From: Yunsheng Lin <linyunsheng@huawei.com>
Date: Sat, 29 Jul 2023 19:40:19 +0800
> On 2023/7/28 21:58, Alexander Lobakin wrote:
>> From: Yunsheng Lin <linyunsheng@huawei.com>
>> Date: Fri, 28 Jul 2023 20:02:51 +0800
>>
>>> On 2023/7/27 22:43, Alexander Lobakin wrote:
>>>> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
>>>
>>> ...
>>>
>>>> +bool page_pool_return_skb_page(struct page *page, bool napi_safe)
>>>
>>> Still having the 'page_pool_' prefix seems odd here when it is in the
>>> skbuff.c where most have skb_ or napi_ prefix, is it better to rename
>>> it to something like napi_return_page_pool_page()?
>>
>> Given that how the function that goes next is named, maybe
>> skb_pp_return_page() (or skb_pp_put_page())?
>
> skb_pp_put_page() seems better.
>
> And I like napi_pp_put_page() with 'napi_' prefix better as
> it does not take a skb as parameter and the naming is aligned
> with the 'napi_safe' parameter.
Ah, I see. Sounds reasonable. I'll pick napi_pp_put_page() for the next
round, I like this one.
>
>>
>>>
>>>> +{
>>>> + struct napi_struct *napi;
>>>> + struct page_pool *pp;
>>>> + bool allow_direct;
>>>> +
>>>> + page = compound_head(page);
>>>> +
>>>> + /* page->pp_magic is OR'ed with PP_SIGNATURE after the allocation
>>>> + * in order to preserve any existing bits, such as bit 0 for the
>>>> + * head page of compound page and bit 1 for pfmemalloc page, so
>>>> + * mask those bits for freeing side when doing below checking,
>>>> + * 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))
>>>> + return false;
>>>> +
>>>> + pp = page->pp;
>>>> +
>>>> + /* Allow direct recycle if we have reasons to believe that we are
>>>> + * in the same context as the consumer would run, so there's
>>>> + * no possible race.
>>>> + */
>>>> + napi = READ_ONCE(pp->p.napi);
>>>> + allow_direct = napi_safe && napi &&
>>>> + READ_ONCE(napi->list_owner) == smp_processor_id();
>>>> +
>>>> + /* Driver set this to memory recycling info. Reset it on recycle.
>>>> + * This will *not* work for NIC using a split-page memory model.
>>>> + * The page will be returned to the pool here regardless of the
>>>> + * 'flipped' fragment being in use or not.
>>>> + */
>>>> + page_pool_put_full_page(pp, page, allow_direct);
>>>> +
>>>> + return true;
>>>> +}
>>>> +EXPORT_SYMBOL(page_pool_return_skb_page);
>>>> +
>>>> static bool skb_pp_recycle(struct sk_buff *skb, void *data, bool napi_safe)
>>
>> (this one)
>>
>>>> {
>>>> if (!IS_ENABLED(CONFIG_PAGE_POOL) || !skb->pp_recycle)
>
> We may need the 'IS_ENABLED(CONFIG_PAGE_POOL' checking in the newly
> moved function too.
The first person who noticed this, for sure we should have it!
>
>>>>
>>
>> Thanks,
>> Olek
>>
>> .
>>
Thanks,
Olek
next prev parent reply other threads:[~2023-08-01 13:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 14:43 [PATCH net-next 0/9] page_pool: a couple of assorted optimizations Alexander Lobakin
2023-07-27 14:43 ` [PATCH net-next 1/9] page_pool: split types and declarations from page_pool.h Alexander Lobakin
2023-07-28 11:58 ` Yunsheng Lin
2023-07-28 13:55 ` Alexander Lobakin
2023-07-27 14:43 ` [PATCH net-next 2/9] net: skbuff: don't include <net/page_pool/types.h> to <linux/skbuff.h> Alexander Lobakin
2023-07-28 12:02 ` Yunsheng Lin
2023-07-28 13:58 ` Alexander Lobakin
2023-07-29 11:40 ` Yunsheng Lin
2023-08-01 13:25 ` Alexander Lobakin [this message]
2023-07-27 14:43 ` [PATCH net-next 3/9] page_pool: place frag_* fields in one cacheline Alexander Lobakin
2023-07-27 14:43 ` [PATCH net-next 4/9] page_pool: shrink &page_pool_params a tiny bit Alexander Lobakin
2023-07-27 14:43 ` [PATCH net-next 5/9] page_pool: don't use driver-set flags field directly Alexander Lobakin
2023-07-28 12:36 ` Yunsheng Lin
2023-07-28 14:03 ` Alexander Lobakin
2023-07-28 15:50 ` Jakub Kicinski
2023-07-29 11:40 ` Yunsheng Lin
2023-08-01 13:36 ` Alexander Lobakin
2023-08-02 11:36 ` Yunsheng Lin
2023-08-02 21:29 ` Jakub Kicinski
2023-08-03 14:56 ` Alexander Lobakin
2023-08-03 16:00 ` Jakub Kicinski
2023-08-03 16:07 ` Alexander Lobakin
2023-08-03 16:40 ` Jakub Kicinski
2023-08-03 16:42 ` Alexander Lobakin
2023-07-27 14:43 ` [PATCH net-next 6/9] page_pool: avoid calling no-op externals when possible Alexander Lobakin
2023-07-28 12:39 ` Yunsheng Lin
2023-07-28 14:14 ` Alexander Lobakin
2023-07-29 12:46 ` Yunsheng Lin
2023-08-01 13:42 ` Alexander Lobakin
2023-08-02 11:37 ` Yunsheng Lin
2023-08-02 15:49 ` Alexander Lobakin
2023-07-27 14:43 ` [PATCH net-next 7/9] net: skbuff: avoid accessing page_pool if !napi_safe when returning page Alexander Lobakin
2023-07-27 14:43 ` [PATCH net-next 8/9] page_pool: add a lockdep check for recycling in hardirq Alexander Lobakin
2023-07-27 14:43 ` [PATCH net-next 9/9] net: skbuff: always try to recycle PP pages directly when in softirq Alexander Lobakin
2023-07-28 9:32 ` Jesper Dangaard Brouer
2023-07-28 13:50 ` Alexander Lobakin
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=61965a16-55bf-2f81-8938-856f834d35bf@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=alexanderduyck@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linyunsheng@huawei.com \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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
all inboxes | Powered by JetHome®