From: Oleksij Rempel <o.rempel@pengutronix.de>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Kory Maincent <kory.maincent@bootlin.com>,
Lukasz Majewski <lukma@denx.de>, Jonathan Corbet <corbet@lwn.net>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Divya.Koppera@microchip.com
Subject: Re: [PATCH net-next v1 1/1] Documentation: networking: add detailed guide on Ethernet flow control configuration
Date: Fri, 18 Jul 2025 09:38:03 +0200 [thread overview]
Message-ID: <aHn526JuMBpUB_T8@pengutronix.de> (raw)
In-Reply-To: <aHkzEalj6tjhQX8N@shell.armlinux.org.uk>
On Thu, Jul 17, 2025 at 06:29:53PM +0100, Russell King (Oracle) wrote:
> On Thu, Jul 17, 2025 at 12:37:02PM +0200, Oleksij Rempel wrote:
> > +Changing the Settings
> > +---------------------
> > +Use `ethtool -A <interface>` to change the settings.
> > +
> > +.. code-block:: bash
> > +
> > + # Enable RX and TX pause, with autonegotiation
> > + ethtool -A eth0 autoneg on rx on tx on
> > +
> > + # Force RX pause on, TX pause off, without autonegotiation
> > + ethtool -A eth0 autoneg off rx on tx off
> > +
> > +**Key Configuration Concepts**:
> > +
> > +* **Autonegotiation Mode**: The recommended mode. The driver programs the PHY
> > + to *advertise* the `rx` and `tx` capabilities. The final active state is
> > + determined by what both sides of the link agree on.
>
> I'm not sure one cal call this "recommended mode", because it doesn't.
> If one specifies tx=0 rx=1, one would expect that the "recommend mode"
> would be tx=0 and rx=1, but if the link partner supports symmetric
> pause, you actually end up with tx=1 and rx=1. If the link partner
> supports only asymmetric, then you end up with tx=0 rx=1 as requested.
>
> Perversely, if you specify tx=1 rx=1, then if the remote supports only
> asymmetric, you end up with everything disabled. Only tx=1 rx=1 is
> supported in this configuration, you can't end up with anything else.
>
> Basically, I don't think calling it "recommended" works.
Ack, I'll drop "recommended".
Would it make sense to also add a short note about the limitations of
link-level flow control? For example, how pause frames can interfere
with traffic prioritization and QoS mechanisms.
--
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 |
prev parent reply other threads:[~2025-07-18 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 10:37 Oleksij Rempel
2025-07-17 17:29 ` Russell King (Oracle)
2025-07-18 7:38 ` Oleksij Rempel [this message]
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=aHn526JuMBpUB_T8@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=Divya.Koppera@microchip.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukma@denx.de \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®