From: Pavel Begunkov <asml.silence@gmail.com>
To: Yunsheng Lin <linyunsheng@huawei.com>,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: skbuff: update comment about pfmemalloc propagating
Date: Mon, 15 May 2023 16:31:13 +0100 [thread overview]
Message-ID: <994ac583-ea4f-2dca-45df-a76d4957b2b2@gmail.com> (raw)
In-Reply-To: <20230515050107.46397-1-linyunsheng@huawei.com>
On 5/15/23 06:01, Yunsheng Lin wrote:
> __skb_fill_page_desc_noacc() is not doing any pfmemalloc
> propagating, and yet it has a comment about that, commit
> 84ce071e38a6 ("net: introduce __skb_fill_page_desc_noacc")
> may have accidentally moved it to __skb_fill_page_desc_noacc(),
> so move it back to __skb_fill_page_desc() which is supposed
> to be doing pfmemalloc propagating.
Looks good,
Reviewed-by: Pavel Begunkov <asml.silence@gmail.com>
> Signed-off-by: Yunsheng Lin <linyunsheng@huawei.com>
> CC: Pavel Begunkov <asml.silence@gmail.com>
> ---
> Also maybe we need a better name for 'noacc' or add some
> comment about that, as 'noacc' seems a little confusing
> for __skb_fill_page_desc_noacc().
It's a known pattern bur in block/ and should be "noacct",
but yeah, it can be more specific.
> ---
> include/linux/skbuff.h | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> index 00e8c435fa1a..4b8d55247198 100644
> --- a/include/linux/skbuff.h
> +++ b/include/linux/skbuff.h
> @@ -2426,11 +2426,6 @@ static inline void __skb_fill_page_desc_noacc(struct skb_shared_info *shinfo,
> {
> skb_frag_t *frag = &shinfo->frags[i];
>
> - /*
> - * Propagate page pfmemalloc to the skb if we can. The problem is
> - * that not all callers have unique ownership of the page but rely
> - * on page_is_pfmemalloc doing the right thing(tm).
> - */
> skb_frag_fill_page_desc(frag, page, off, size);
> }
>
> @@ -2463,6 +2458,11 @@ static inline void __skb_fill_page_desc(struct sk_buff *skb, int i,
> struct page *page, int off, int size)
> {
> __skb_fill_page_desc_noacc(skb_shinfo(skb), i, page, off, size);
> +
> + /* Propagate page pfmemalloc to the skb if we can. The problem is
> + * that not all callers have unique ownership of the page but rely
> + * on page_is_pfmemalloc doing the right thing(tm).
> + */
> page = compound_head(page);
> if (page_is_pfmemalloc(page))
> skb->pfmemalloc = true;
--
Pavel Begunkov
next prev parent reply other threads:[~2023-05-15 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 5:01 [PATCH net-next] net: skbuff: update comment about pfmemalloc propagating Yunsheng Lin
2023-05-15 15:31 ` Pavel Begunkov [this message]
2023-05-16 8:20 ` 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=994ac583-ea4f-2dca-45df-a76d4957b2b2@gmail.com \
--to=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.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