From: Yunsheng Lin <linyunsheng@huawei.com>
To: Liang Chen <liangchen.linux@gmail.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<hawk@kernel.org>, <ilias.apalodimas@linaro.org>
Cc: <netdev@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH net-next v3 1/3] page_pool: Rename pp_frag_count to pp_ref_count
Date: Sat, 25 Nov 2023 19:53:13 +0800 [thread overview]
Message-ID: <a45e4183-3ac3-2853-810a-63c7277d6318@huawei.com> (raw)
In-Reply-To: <20231124073439.52626-2-liangchen.linux@gmail.com>
On 2023/11/24 15:34, Liang Chen wrote:
> static inline void page_pool_fragment_page(struct page *page, long nr)
It seems page_pool_fragment_page() might not be a appropriate name too?
Perhaps it might be better to grep defrag/frag to see if there is other
function name might need changing.
> {
> - atomic_long_set(&page->pp_frag_count, nr);
> + atomic_long_set(&page->pp_ref_count, nr);
> }
>
> -static inline long page_pool_defrag_page(struct page *page, long nr)
> +static inline long page_pool_deref_page(struct page *page, long nr)
page_pool_defrag_page() related function is called by mlx5 driver directly,
we need to change it to use the new function too.
I assume that deref is short for dereference? According to:
https://stackoverflow.com/questions/4955198/what-does-dereferencing-a-pointer-mean-in-c-c
'dereferencing means accessing the value from a certain memory location
against which that pointer is pointing'.
So I am not sure if 'deref' is the right word here as I am not a native
english speaker, But it seems 'unref' is more appropriate here if we mirror
the napi_frag_unref() function name?
next prev parent reply other threads:[~2023-11-25 11:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 7:34 [PATCH net-next v3 0/3] skbuff: Optimize SKB coalescing for page pool Liang Chen
2023-11-24 7:34 ` [PATCH net-next v3 1/3] page_pool: Rename pp_frag_count to pp_ref_count Liang Chen
2023-11-25 11:53 ` Yunsheng Lin [this message]
2023-11-27 4:21 ` Liang Chen
2023-11-24 7:34 ` [PATCH net-next v3 2/3] page_pool: halve BIAS_MAX for fragment multiple user references Liang Chen
2023-11-25 12:01 ` Yunsheng Lin
2023-11-27 4:22 ` Liang Chen
2023-11-24 7:34 ` [PATCH net-next v3 3/3] skbuff: Optimization of SKB coalescing for page pool Liang Chen
2023-11-25 12:16 ` Yunsheng Lin
2023-11-27 4:23 ` Liang Chen
2023-11-27 10:48 ` Yunsheng Lin
2023-11-28 10:41 ` 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=a45e4183-3ac3-2853-810a-63c7277d6318@huawei.com \
--to=linyunsheng@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=liangchen.linux@gmail.com \
--cc=linux-mm@kvack.org \
--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