From: Kory Maincent <kory.maincent@bootlin.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
kernel@pengutronix.de,
Dent Project <dentproject@linuxfoundation.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Kyle Swenson <kyle.swenson@est.tech>
Subject: Re: [PATCH net-next 2/2] net: pse-pd: pd692x0: Add sysfs interface for configuration save/reset
Date: Thu, 28 Aug 2025 13:29:01 +0200 [thread overview]
Message-ID: <20250828132901.76e00334@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <20250825151422.4cd1ea72@kernel.org>
Le Mon, 25 Aug 2025 15:14:22 -0700,
Jakub Kicinski <kuba@kernel.org> a écrit :
> On Mon, 25 Aug 2025 14:18:25 +0200 Andrew Lunn wrote:
> > On Mon, Aug 25, 2025 at 11:14:03AM +0200, Oleksij Rempel wrote:
> > > On Mon, Aug 25, 2025 at 10:47:21AM +0200, Kory Maincent wrote:
> [...]
> [...]
> > >
> > > My personal preference would be to use devlink (netlink based)
> > > interface.
> >
> > Yes, devlink also crossed my mind, probably devlink params. Although
> > saving the current configuration to non-volatile memory is more a meta
> > parameter.
>
> This is a bit of a perennial topic. Most datacenter NIC vendors have
> a way to save link settings and alike to flash. None bothered with
> adding upstream APIs tho. If the configs are fully within ethtool
> I think we should be able to add an ethtool header flag that says
> "this config request is to be written to flash". And vice versa
> (get should read from flash)?
In fact there is the managers power budget parameter taken from the devicetree
which is not in ethtool config. It could be reconfigured after each reboot or
conf reset but it is an example of non ethtool configuration and more could
appear in the future. Talking about perennial, ethtool is then maybe not a good
idea because we still will need a way to save these new global configurations
saved to the non-volatile mem.
I am not really familiar with devlink but indeed after a quick look devlink
seems more suitable for the PSE global configurations.
I don't really know if we should use devlink param and devlink reload or only
devlink param or a new devlink conf.
Or we could save the configuration on every change but it will bring 70ms (I2C
read/write + store waiting time) latency for every command.
> Resetting would work either via devlink reload, or ethtool --reset,
> don't think we even need any API addition there.
Is there no way for NIC to reset their configuration except through ethtool
reload?
PS: got a client mail issue so you might have receive two mails. Sorry for that.
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-08-28 11:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 15:37 [PATCH net-next 0/2] net: pse-pd: pd692x0: Add permanent configuration management support Kory Maincent
2025-08-22 15:37 ` [PATCH net-next 1/2] net: pse-pd: pd692x0: Separate configuration parsing from hardware setup Kory Maincent
2025-08-25 22:10 ` Jakub Kicinski
2025-08-28 8:46 ` Kory Maincent
2025-08-28 22:12 ` Jakub Kicinski
2025-08-29 8:26 ` Kory Maincent
2025-08-29 23:58 ` Jakub Kicinski
2025-08-22 15:37 ` [PATCH net-next 2/2] net: pse-pd: pd692x0: Add sysfs interface for configuration save/reset Kory Maincent
2025-08-22 17:17 ` Andrew Lunn
2025-08-25 8:47 ` Kory Maincent
2025-08-25 9:14 ` Oleksij Rempel
2025-08-25 12:18 ` Andrew Lunn
2025-08-25 22:14 ` Jakub Kicinski
2025-08-28 11:29 ` Kory Maincent [this message]
2025-08-28 22:15 ` Jakub Kicinski
2025-08-25 12:20 ` 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=20250828132901.76e00334@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dentproject@linuxfoundation.org \
--cc=edumazet@google.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=kyle.swenson@est.tech \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--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