From: Stanislav Fomichev <stfomichev@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, donald.hunter@gmail.com,
netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, sdf@fomichev.me,
joe@dama.to, jstancek@redhat.com
Subject: Re: [PATCH net-next 0/5] tools: ynl: turn the page-pool sample into a real tool
Date: Thu, 6 Nov 2025 08:34:57 -0800 [thread overview]
Message-ID: <aQzOMawFQHUcUT-X@mini-arch> (raw)
In-Reply-To: <20251106070247.7dcefc97@kernel.org>
On 11/06, Jakub Kicinski wrote:
> On Tue, 4 Nov 2025 15:23:43 -0800 Jakub Kicinski wrote:
> > The page-pool YNL sample is quite useful. It's helps calculate
> > recycling rate and memory consumption. Since we still haven't
> > figured out a way to integrate with iproute2 (not for the lack
> > of thinking how to solve it) - create a ynltool command in ynl.
> >
> > Add page-pool and qstats support.
> >
> > Most commands can use the Python YNL CLI directly but low level
> > stats often need aggregation or some math on top to be useful.
> > Specifically in this patch set:
> > - page pool stats are aggregated and recycling rate computed
> > - per-queue stats are used to compute traffic balance across queues
>
> FWIW I'd appreciate any feedback here. It's hard to draw the line
> on what to implement in a tool like ynltool and what to leave for
> the YNL Python directly.
I like the idea. Python is useful for local development, but shipping
it (as of now) is a bit painful. I'm not sure what's the line gonna
be between iproute2 vs ethtool vs ynltool, but I think we can figure
it out as we go.
next prev parent reply other threads:[~2025-11-06 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 23:23 [PATCH net-next 0/5] tools: ynl: turn the page-pool sample into a real tool Jakub Kicinski
2025-11-04 23:23 ` [PATCH net-next 1/5] netlink: specs: netdev add missing stats to qstat-get Jakub Kicinski
2025-11-04 23:23 ` [PATCH net-next 2/5] tools: ynltool: create skeleton for the C command Jakub Kicinski
2025-11-06 16:37 ` Stanislav Fomichev
2025-11-06 22:24 ` Jakub Kicinski
2025-11-04 23:23 ` [PATCH net-next 3/5] tools: ynltool: add page-pool stats Jakub Kicinski
2025-11-04 23:23 ` [PATCH net-next 4/5] tools: ynltool: add qstats support Jakub Kicinski
2025-11-04 23:23 ` [PATCH net-next 5/5] tools: ynltool: add traffic distribution balance Jakub Kicinski
2025-11-06 15:02 ` [PATCH net-next 0/5] tools: ynl: turn the page-pool sample into a real tool Jakub Kicinski
2025-11-06 16:34 ` Stanislav Fomichev [this message]
2025-11-07 16:10 ` 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=aQzOMawFQHUcUT-X@mini-arch \
--to=stfomichev@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joe@dama.to \
--cc=jstancek@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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.