netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <hawk@kernel.org>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: netdev@vger.kernel.org, linux-mm@kvack.org, kuba@kernel.org,
	ilias.apalodimas@linaro.org, jasowang@redhat.com,
	linyunsheng@huawei.com, Liang Chen <liangchen.linux@gmail.com>,
	edumazet@google.com, davem@davemloft.net, almasrymina@google.com,
	pabeni@redhat.com
Subject: Re: [PATCH net-next v8 2/4] page_pool: halve BIAS_MAX for multiple user references of a fragment
Date: Mon, 11 Dec 2023 11:12:01 +0100	[thread overview]
Message-ID: <6f7f7724-12a0-45d5-80dc-a811b58783c8@kernel.org> (raw)
In-Reply-To: <20231211035243.15774-3-liangchen.linux@gmail.com>

Hi Alex,

For page_pool BIAS stuff I would really appreciate your review please.
-Jesper


On 11/12/2023 04.52, Liang Chen wrote:
> Referring to patch [1], in order to support multiple users referencing the
> same fragment and prevent overflow from pp_ref_count growing, the initial
> value of pp_ref_count is halved, leaving room for pp_ref_count to increment
> before the page is drained.
> 
> [1]
> https://lore.kernel.org/all/20211009093724.10539-3-linyunsheng@huawei.com/
> 
> Signed-off-by: Liang Chen <liangchen.linux@gmail.com>
> Reviewed-by: Yunsheng Lin <linyunsheng@huawei.com>
> ---
>   net/core/page_pool.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/net/core/page_pool.c b/net/core/page_pool.c
> index 106220b1f89c..436f7ffea7b4 100644
> --- a/net/core/page_pool.c
> +++ b/net/core/page_pool.c
> @@ -26,7 +26,7 @@
>   #define DEFER_TIME (msecs_to_jiffies(1000))
>   #define DEFER_WARN_INTERVAL (60 * HZ)
>   
> -#define BIAS_MAX	LONG_MAX
> +#define BIAS_MAX	(LONG_MAX >> 1)
>   
>   #ifdef CONFIG_PAGE_POOL_STATS
>   /* alloc_stat_inc is intended to be used in softirq context */

  reply	other threads:[~2023-12-11 10:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11  3:52 [PATCH net-next v8 0/4] skbuff: Optimize SKB coalescing for page pool Liang Chen
2023-12-11  3:52 ` [PATCH net-next v8 1/4] page_pool: transition to reference count management after page draining Liang Chen
2023-12-11  7:43   ` Ilias Apalodimas
2023-12-11  3:52 ` [PATCH net-next v8 2/4] page_pool: halve BIAS_MAX for multiple user references of a fragment Liang Chen
2023-12-11 10:12   ` Jesper Dangaard Brouer [this message]
2023-12-11  3:52 ` [PATCH net-next v8 3/4] skbuff: Add a function to check if a page belongs to page_pool Liang Chen
2023-12-11  7:40   ` Ilias Apalodimas
2023-12-11  3:52 ` [PATCH net-next v8 4/4] skbuff: Optimization of SKB coalescing for page pool Liang Chen
2023-12-11  7:46   ` Ilias Apalodimas
2023-12-11 20:14     ` Jakub Kicinski
2023-12-12  3:00       ` Liang Chen
2023-12-13  7:09       ` Ilias Apalodimas
2023-12-14  2:26         ` Liang Chen
2023-12-14  2:34           ` Jakub Kicinski
2023-12-14  2:46             ` 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=6f7f7724-12a0-45d5-80dc-a811b58783c8@kernel.org \
    --to=hawk@kernel.org \
    --cc=alexander.duyck@gmail.com \
    --cc=almasrymina@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --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;
as well as URLs for NNTP newsgroup(s).