linux-kernel - Re: [PATCH net-next v6 06/12] net: pse-pd: Add support for budget evaluation strategies

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z-GXROTptwg3jh4J@p620>
Date: Mon, 24 Mar 2025 17:33:18 +0000
From: Kyle Swenson <kyle.swenson@....tech>
To: Kory Maincent <kory.maincent@...tlin.com>
CC: Oleksij Rempel <o.rempel@...gutronix.de>, Andrew Lunn <andrew@...n.ch>,
	"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Jonathan
 Corbet <corbet@....net>, Donald Hunter <donald.hunter@...il.com>, Rob Herring
	<robh@...nel.org>, Andrew Lunn <andrew+netdev@...n.ch>, Simon Horman
	<horms@...nel.org>, Heiner Kallweit <hkallweit1@...il.com>, Russell King
	<linux@...linux.org.uk>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor
 Dooley <conor+dt@...nel.org>, Liam Girdwood <lgirdwood@...il.com>, Mark Brown
	<broonie@...nel.org>, Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>, Dent Project
	<dentproject@...uxfoundation.org>, "kernel@...gutronix.de"
	<kernel@...gutronix.de>, Maxime Chevallier <maxime.chevallier@...tlin.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next v6 06/12] net: pse-pd: Add support for budget
 evaluation strategies

Hello Kory,

On Mon, Mar 24, 2025 at 05:39:07PM +0100, Kory Maincent wrote:
> Hello Kyle, Oleksij,
...
> 
> Small question on PSE core behavior for PoE users.
> 
> If we want to enable a port but we can't due to over budget.
> Should we :
> - Report an error (or not) and save the enable action from userspace. On that
>   case, if enough budget is available later due to priority change or port
>   disconnected the PSE core will try automatically to re enable the PoE port.
>   The port will then be enabled without any action from the user.
> - Report an error but do nothing. The user will need to rerun the enable
>   command later to try to enable the port again.
> 
> How is it currently managed in PoE poprietary userspace tools?

So in our implementation, we're using the first option you've presented.
That is, we save the enable action from the user and if we can't power
the device due to insufficient budget remaining, we'll indicate that status to the
user.  If enough power budget becomes available later, we'll power up
the device automatically.

Hope this helps,
Kyle