From: Joe Damato <jdamato@fastly.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: netdev@vger.kernel.org, lorenzo.bianconi@redhat.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
jbrouer@redhat.com, ilias.apalodimas@linaro.org
Subject: Re: [PATCH net-next] page_pool: Add recycle stats to page_pool_put_page_bulk
Date: Wed, 6 Apr 2022 16:15:13 -0700 [thread overview]
Message-ID: <20220406231512.GB96269@fastly.com> (raw)
In-Reply-To: <1921137145a6a20bb3494c72b33268f5d6d86834.1649191881.git.lorenzo@kernel.org>
On Tue, Apr 05, 2022 at 10:52:55PM +0200, Lorenzo Bianconi wrote:
> Add missing recycle stats to page_pool_put_page_bulk routine.
Thanks for proposing this change. I did miss this path when adding
stats.
I'm sort of torn on this. It almost seems that we might want to track
bulking events separately as their own stat.
Maybe Ilias has an opinion on this; I did implement the stats, but I'm not
a maintainer of the page_pool so I'm not sure what I think matters all
that much ;)
> Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
> ---
> net/core/page_pool.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/net/core/page_pool.c b/net/core/page_pool.c
> index 1943c0f0307d..4af55d28ffa3 100644
> --- a/net/core/page_pool.c
> +++ b/net/core/page_pool.c
> @@ -36,6 +36,12 @@
> this_cpu_inc(s->__stat); \
> } while (0)
>
> +#define recycle_stat_add(pool, __stat, val) \
> + do { \
> + struct page_pool_recycle_stats __percpu *s = pool->recycle_stats; \
> + this_cpu_add(s->__stat, val); \
> + } while (0)
> +
> bool page_pool_get_stats(struct page_pool *pool,
> struct page_pool_stats *stats)
> {
> @@ -63,6 +69,7 @@ EXPORT_SYMBOL(page_pool_get_stats);
> #else
> #define alloc_stat_inc(pool, __stat)
> #define recycle_stat_inc(pool, __stat)
> +#define recycle_stat_add(pool, __stat, val)
> #endif
>
> static int page_pool_init(struct page_pool *pool,
> @@ -566,9 +573,13 @@ void page_pool_put_page_bulk(struct page_pool *pool, void **data,
> /* Bulk producer into ptr_ring page_pool cache */
> page_pool_ring_lock(pool);
> for (i = 0; i < bulk_len; i++) {
> - if (__ptr_ring_produce(&pool->ring, data[i]))
> - break; /* ring full */
> + if (__ptr_ring_produce(&pool->ring, data[i])) {
> + /* ring full */
> + recycle_stat_inc(pool, ring_full);
> + break;
> + }
> }
> + recycle_stat_add(pool, ring, i);
If we do go with this approach (instead of adding bulking-specific stats),
we might want to replicate this change in __page_pool_alloc_pages_slow; we
currently only count the single allocation returned by the slow path, but
the rest of the pages which refilled the cache are not counted.
> page_pool_ring_unlock(pool);
>
> /* Hopefully all pages was return into ptr_ring */
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-04-06 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 20:52 [PATCH net-next] page_pool: Add recycle stats to page_pool_put_page_bulk Lorenzo Bianconi
2022-04-06 23:15 ` Joe Damato [this message]
2022-04-07 7:43 ` Lorenzo Bianconi
2022-04-07 20:14 ` Ilias Apalodimas
2022-04-09 5:22 ` Joe Damato
2022-04-09 10:22 ` Ilias Apalodimas
2022-04-09 17:17 ` Lorenzo Bianconi
2022-04-09 17:20 ` Joe Damato
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=20220406231512.GB96269@fastly.com \
--to=jdamato@fastly.com \
--cc=davem@davemloft.net \
--cc=ilias.apalodimas@linaro.org \
--cc=jbrouer@redhat.com \
--cc=kuba@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.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;
as well as URLs for NNTP newsgroup(s).