Netdev List
 help / color / mirror / Atom feed
From: Kory Maincent <kory.maincent@bootlin.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Andrew Lunn <andrew@lunn.ch>, Michal Kubecek <mkubecek@suse.cz>,
	Dent Project <dentproject@linuxfoundation.org>,
	Kyle Swenson <kyle.swenson@est.tech>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH ethtool v2 2/3] ethtool: pse-pd: Add PSE priority support
Date: Wed, 13 Aug 2025 14:57:30 +0200	[thread overview]
Message-ID: <20250813145730.0b47e26e@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <aJyEMob8kFAvD-HU@pengutronix.de>

Le Wed, 13 Aug 2025 14:25:22 +0200,
Oleksij Rempel <o.rempel@pengutronix.de> a écrit :

> Hi Kory,
> 
> Thank you for your work! Here are some review comments...

Hello Oleksij,

> 
> On Wed, Aug 13, 2025 at 10:57:51AM +0200, Kory Maincent wrote:
> > From: Kory Maincent (Dent Project) <kory.maincent@bootlin.com>
> > 
> > Add support for PSE (Power Sourcing Equipment) priority management:
> > - Add priority configuration parameter (prio) for port priority management
> > - Display power domain index, maximum priority, and current priority
> > 
> > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> > ---
> >  ethtool.8.in     | 13 +++++++++++++
> >  ethtool.c        |  1 +
> >  netlink/pse-pd.c | 29 +++++++++++++++++++++++++++++
> >  3 files changed, 43 insertions(+)
> > 
> > diff --git a/ethtool.8.in b/ethtool.8.in
> > index 29b8a8c..163b2b0 100644
> > --- a/ethtool.8.in
> > +++ b/ethtool.8.in
> > @@ -561,6 +561,7 @@ ethtool \- query or control network driver and hardware
> > settings .RB [ c33\-pse\-admin\-control
> >  .BR enable | disable ]
> >  .BN c33\-pse\-avail\-pw\-limit N
> > +.BN prio N
> >  .HP
> >  .B ethtool \-\-flash\-module\-firmware
> >  .I devname
> > @@ -1911,6 +1912,15 @@ This attribute specifies the allowed power limit
> > ranges in mW for configuring the c33-pse-avail-pw-limit parameter. It
> > defines the valid power levels that can be assigned to the c33 PSE in
> > compliance with the c33 standard.
> > +.TP
> > +.B power-domain-index
> > +This attribute defines the index of the PSE Power Domain.  
> 
> May be:
> 
> Reports the index of the PSE power domain the port belongs to. Every
> port belongs to exactly one power domain. Port priorities are defined
> within that power domain.
> 
> Each power domain may have its own maximum budget (e.g., 100 W per
> domain) in addition to a system-wide budget (e.g., 200 W overall).
> Domain limits are enforced first: if a single domain reaches its budget,
> only ports in that domain are affected. The system-wide budget is
> enforced across all domains; only when it is exceeded do cross-domain
> priorities apply.

Thanks for the doc review!
Maybe we should not talking about cross-domain priority yet, we don't know how
PSE are supposed to behave on that specific case. 

...

> > +	if (tb[ETHTOOL_A_PSE_PRIO]) {
> > +		u32 val;
> > +
> > +		val = mnl_attr_get_u32(tb[ETHTOOL_A_PSE_PRIO]);
> > +		print_uint(PRINT_ANY, "priority", "Priority %u\n", val);  
> 
> missing colon
> 		print_uint(PRINT_ANY, "priority", "Priority: %u\n", val);

Well spotted, thanks!

Regards,
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

  reply	other threads:[~2025-08-13 12:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13  8:57 [PATCH ethtool v2 0/3] Add support for PSE priority feature and PSE event monitoring Kory Maincent
2025-08-13  8:57 ` [PATCH ethtool v2 1/3] update UAPI header copies Kory Maincent
2025-08-13  8:57 ` [PATCH ethtool v2 2/3] ethtool: pse-pd: Add PSE priority support Kory Maincent
2025-08-13 12:25   ` Oleksij Rempel
2025-08-13 12:57     ` Kory Maincent [this message]
2025-08-13  8:57 ` [PATCH ethtool v2 3/3] ethtool: pse-pd: Add PSE event monitoring support Kory Maincent
2025-08-13 12:44   ` Oleksij Rempel
2025-08-13 13:22     ` Kory Maincent

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=20250813145730.0b47e26e@kmaincent-XPS-13-7390 \
    --to=kory.maincent@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dentproject@linuxfoundation.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kyle.swenson@est.tech \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=thomas.petazzoni@bootlin.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