linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Donald Hunter <donald.hunter@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Simon Horman <horms@kernel.org>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	Kyle Swenson <kyle.swenson@est.tech>,
	Dent Project <dentproject@linuxfoundation.org>,
	kernel@pengutronix.de,
	Maxime Chevallier <maxime.chevallier@bootlin.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 07/12] net: ethtool: Add PSE new budget evaluation strategy support feature
Date: Fri, 21 Feb 2025 14:49:21 +0100	[thread overview]
Message-ID: <Z7iEYQzsdpUFmfZE@pengutronix.de> (raw)
In-Reply-To: <20250218-feature_poe_port_prio-v5-7-3da486e5fd64@bootlin.com>

Hi Kory,

On Tue, Feb 18, 2025 at 05:19:11PM +0100, Kory Maincent wrote:
> From: Kory Maincent (Dent Project) <kory.maincent@bootlin.com>
> 
> This patch expands the status information provided by ethtool for PSE c33
> with current port priority and max port priority. It also adds a call to
> pse_ethtool_set_prio() to configure the PSE port priority.

Thank you! Here are some comments...

> --- a/Documentation/networking/ethtool-netlink.rst
> +++ b/Documentation/networking/ethtool-netlink.rst
> @@ -1790,6 +1790,12 @@ Kernel response contents:
>    ``ETHTOOL_A_C33_PSE_PW_LIMIT_RANGES``       nested  Supported power limit
>                                                        configuration ranges.
>    ``ETHTOOL_A_PSE_PW_D_ID``                      u32  Index of the PSE power domain
> +  ``ETHTOOL_A_C33_PSE_BUDGET_EVAL_STRAT``        u32  Budget evaluation strategy
> +                                                      of the PSE
> +  ``ETHTOOL_A_C33_PSE_PRIO_MAX``                 u32  Priority maximum configurable
> +                                                      on the PoE PSE
> +  ``ETHTOOL_A_C33_PSE_PRIO``                     u32  Priority of the PoE PSE
> +                                                      currently configured

Please remove _C33_ from these fields, as they are not specific to Clause 33.

>    ==========================================  ======  =============================
>  
>  When set, the optional ``ETHTOOL_A_PODL_PSE_ADMIN_STATE`` attribute identifies
> @@ -1866,6 +1872,51 @@ equal.
>  The ``ETHTOOL_A_PSE_PW_D_ID`` attribute identifies the index of PSE power
>  domain.
>  
> +When set, the optional ``ETHTOOL_A_C33_PSE_PRIO_SUPP_MODES`` attribute
> +identifies the priority mode supported by the C33 PSE.
> +When set, the optional ``ETHTOOL_A_C33_PSE_BUDGET_EVAL_STRAT`` attributes is used to
> +identifies the currently configured C33 PSE budget evaluation strategy.
> +The available strategies are:
> +
> +1. Disabled:
> +
> +   In this mode, the port is excluded from active budget evaluation. It
> +   allows the port to violate the budget and is intended primarily for testing
> +   purposes.
> +
> +2. Static Method:
> +
> +   This method involves distributing power based on PD classification. It’s
> +   straightforward and stable, with the PSE core keeping track of the budget
> +   and subtracting the power requested by each PD’s class. This is the
> +   safest option and should be used by default.
> +
> +   Advantages: Every PD gets its promised power at any time, which guarantees
> +   reliability.
> +
> +   Disadvantages: PD classification steps are large, meaning devices request
> +   much more power than they actually need. As a result, the power supply may
> +   only operate at, say, 50% capacity, which is inefficient and wastes money.
> +
> +3. Dynamic Method:
> +
> +   This method monitors the current consumption per port and subtracts it from
> +   the available power budget. When the budget is exceeded, lower-priority
> +   ports are shut down. This method is managed by the PSE controller itself.
> +
> +   Advantages: This method optimizes resource utilization, saving costs.
> +
> +   Disadvantages: Low-priority devices may experience instability.
> +
> +.. kernel-doc:: include/uapi/linux/ethtool.h
> +    :identifiers: ethtool_pse_budget_eval_strategies
> +
> +When set, the optional ``ETHTOOL_A_C33_PSE_PRIO_MAX`` attribute identifies
> +the C33 PSE maximum priority value.
> +When set, the optional ``ETHTOOL_A_C33_PSE_PRIO`` attributes is used to
> +identifies the currently configured C33 PSE priority.
> +For a description of PSE priority attributes, see ``PSE_SET``.
> +
>  PSE_SET
>  =======
>  
> @@ -1879,6 +1930,8 @@ Request contents:
>    ``ETHTOOL_A_C33_PSE_ADMIN_CONTROL``        u32  Control PSE Admin state
>    ``ETHTOOL_A_C33_PSE_AVAIL_PWR_LIMIT``      u32  Control PoE PSE available
>                                                    power limit
> +  ``ETHTOOL_A_C33_PSE_PRIO``                 u32  Control priority of the
> +                                                  PoE PSE

Please remove _C33_ from these field, as they are not specific to
Clause 33.
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2025-02-21 13:50 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 16:19 [PATCH net-next v5 00/12] Add support for PSE budget evaluation strategy Kory Maincent
2025-02-18 16:19 ` [PATCH net-next v5 01/12] net: ethtool: Add support for ethnl_info_init_ntf helper function Kory Maincent
2025-02-18 16:19 ` [PATCH net-next v5 02/12] net: pse-pd: Add support for reporting events Kory Maincent
2025-02-21  0:42   ` Jakub Kicinski
2025-02-24 12:33     ` Kory Maincent
2025-02-24 21:47       ` Jakub Kicinski
2025-02-21  8:50   ` Oleksij Rempel
2025-02-24 11:02     ` Kory Maincent
2025-02-24 18:19       ` Kory Maincent
2025-02-18 16:19 ` [PATCH net-next v5 03/12] net: pse-pd: tps23881: Add support for PSE events and interrupts Kory Maincent
2025-02-18 16:19 ` [PATCH net-next v5 04/12] net: pse-pd: Add support for PSE power domains Kory Maincent
2025-02-21  0:43   ` Jakub Kicinski
2025-02-18 16:19 ` [PATCH net-next v5 05/12] net: ethtool: Add support for new power domains index description Kory Maincent
2025-02-18 16:19 ` [PATCH net-next v5 06/12] net: pse-pd: Add support for budget evaluation strategies Kory Maincent
2025-02-21  0:51   ` Jakub Kicinski
2025-02-24 13:10     ` Kory Maincent
2025-02-24 21:45       ` Jakub Kicinski
2025-02-25  9:25         ` Kory Maincent
2025-02-26  1:47           ` Jakub Kicinski
2025-02-26  5:59             ` Oleksij Rempel
2025-02-26  6:06               ` Oleksij Rempel
2025-02-27  2:42                 ` Jakub Kicinski
2025-02-27  7:40                   ` Oleksij Rempel
2025-02-27 14:57                     ` Kory Maincent
2025-02-27 16:40                       ` Oleksij Rempel
2025-02-27 18:26                         ` Kory Maincent
2025-03-01 13:00                           ` Oleksij Rempel
2025-03-03 13:40                             ` Kory Maincent
2025-03-04  1:12                               ` Jakub Kicinski
2025-02-18 16:19 ` [PATCH net-next v5 07/12] net: ethtool: Add PSE new budget evaluation strategy support feature Kory Maincent
2025-02-21 13:49   ` Oleksij Rempel [this message]
2025-02-24 13:13     ` Kory Maincent
2025-02-18 16:19 ` [PATCH net-next v5 08/12] net: pse-pd: pd692x0: Add support for PSE PI priority feature Kory Maincent
2025-02-18 16:19 ` [PATCH net-next v5 09/12] net: pse-pd: pd692x0: Add support for controller and manager power supplies Kory Maincent
2025-02-24 12:42   ` Maxime Chevallier
2025-02-24 12:49     ` Russell King (Oracle)
2025-02-24 13:17       ` Maxime Chevallier
2025-02-18 16:19 ` [PATCH net-next v5 10/12] dt-bindings: net: pse-pd: microchip,pd692x0: Add manager regulator supply Kory Maincent
2025-02-19  7:41   ` Krzysztof Kozlowski
2025-02-18 16:19 ` [PATCH net-next v5 11/12] net: pse-pd: tps23881: Add support for static port priority feature Kory Maincent
2025-02-18 16:19 ` [PATCH net-next v5 12/12] dt-bindings: net: pse-pd: ti,tps23881: Add interrupt description Kory Maincent
2025-02-19  7:41   ` Krzysztof Kozlowski

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=Z7iEYQzsdpUFmfZE@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dentproject@linuxfoundation.org \
    --cc=devicetree@vger.kernel.org \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=kory.maincent@bootlin.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kyle.swenson@est.tech \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).