All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Tariq Toukan <ttoukan.linux@gmail.com>
Cc: linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Joe Damato <jdamato@fastly.com>,
	Leon Romanovsky <leon@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH net-next] net/mlnx5: Use generic code for page_pool statistics.
Date: Wed, 5 Mar 2025 21:20:55 +0100	[thread overview]
Message-ID: <20250305202055.MHFrfQRO@linutronix.de> (raw)
In-Reply-To: <8168a8ee-ad2f-46c5-b48e-488a23243b3d@gmail.com>

On 2025-03-05 21:44:23 [+0200], Tariq Toukan wrote:
> Hi,

Hi,

> Thanks for your patch.
> 
> IIUC you remove here the per-ring page_pool stats, and keep only the summed
> stats.
> 
> I guess the reason for this is that the page_pool strings have no per-ring
> variants.
> 
>   59 static const char pp_stats[][ETH_GSTRING_LEN] = {
>   60         "rx_pp_alloc_fast",
>   61         "rx_pp_alloc_slow",
>   62         "rx_pp_alloc_slow_ho",
>   63         "rx_pp_alloc_empty",
>   64         "rx_pp_alloc_refill",
>   65         "rx_pp_alloc_waive",
>   66         "rx_pp_recycle_cached",
>   67         "rx_pp_recycle_cache_full",
>   68         "rx_pp_recycle_ring",
>   69         "rx_pp_recycle_ring_full",
>   70         "rx_pp_recycle_released_ref",
>   71 };
> 
> Is this the only reason?

Yes. I haven't seen any reason to keep it. It is only copied around.

> I like the direction of this patch, but we won't give up the per-ring
> counters. Please keep them.

Hmm. Okay. I guess I could stuff a struct there. But it really looks
like waste since it is not used.

> I can think of a new "customized page_pool counters strings" API, where the
> strings prefix is provided by the driver, and used to generate the per-pool
> strings.

Okay. So I make room for it and you wire it up ;)

Sebastian

  reply	other threads:[~2025-03-05 20:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 12:14 [PATCH net-next] net/mlnx5: Use generic code for page_pool statistics Sebastian Andrzej Siewior
2025-03-05 16:21 ` Andrew Lunn
2025-03-05 16:26   ` Sebastian Andrzej Siewior
2025-03-05 17:43     ` Andrew Lunn
2025-03-05 18:52       ` Sebastian Andrzej Siewior
2025-03-05 19:44 ` Tariq Toukan
2025-03-05 20:20   ` Sebastian Andrzej Siewior [this message]
2025-03-06  6:49     ` Tariq Toukan
2025-03-06  7:38       ` Sebastian Andrzej Siewior
2025-03-06  8:32     ` Sebastian Andrzej Siewior
2025-03-06  9:50       ` Tariq Toukan
2025-03-06  9:56         ` Sebastian Andrzej Siewior
2025-03-06 10:22           ` Tariq Toukan
2025-03-06 10:38             ` Sebastian Andrzej Siewior
2025-03-06 11:10           ` Tariq Toukan
2025-03-06 13:16             ` Sebastian Andrzej Siewior

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=20250305202055.MHFrfQRO@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jdamato@fastly.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=tglx@linutronix.de \
    --cc=ttoukan.linux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.