[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230411143340.cguwmjbyi2tyrjh2@skbuf>
Date: Tue, 11 Apr 2023 17:33:40 +0300
From: Vladimir Oltean <olteanv@...il.com>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Andrew Lunn <andrew@...n.ch>, Jakub Kicinski <kuba@...nel.org>,
Oleksij Rempel <o.rempel@...gutronix.de>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Florian Fainelli <f.fainelli@...il.com>,
Paolo Abeni <pabeni@...hat.com>,
Woojung Huh <woojung.huh@...rochip.com>,
Arun Ramadoss <arun.ramadoss@...rochip.com>,
kernel@...gutronix.de, UNGLinuxDriver@...rochip.com,
netdev@...r.kernel.org
Subject: Re: FWD: Re: [PATCH net-next v1 1/1] net: dsa: microchip: ksz8: Make
flow control, speed, and duplex on CPU port configurable
On Fri, Apr 07, 2023 at 06:44:20PM +0100, Russell King (Oracle) wrote:
> Lastly, a more general question for ethtool/network folk - as for half
> duplex and back pressure, is that a recognised facility for the MAC
> to control via the ethtool pause parameter API?
AFAIU, the ethtool pause API is for PAUSE-based flow control (as defined
in IEEE 802.3-2018 annex 31B), not half duplex collision based flow control.
That being said, I don't know what facility could be used to enable
collision based flow control. I'd say it is an abuse of the API.
Powered by blists - more mailing lists