All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Asmaa Mnebhi <asmaa@nvidia.com>
Cc: David Thompson <davthompson@nvidia.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Liming Sun <limings@nvidia.com>
Subject: Re: [PATCH net-next v5] Add Mellanox BlueField Gigabit Ethernet driver
Date: Tue, 1 Jun 2021 16:12:29 +0200	[thread overview]
Message-ID: <YLZATclYESd9ROcd@lunn.ch> (raw)
In-Reply-To: <CH2PR12MB38955E99161C89C165D70B76D73E9@CH2PR12MB3895.namprd12.prod.outlook.com>

> I guess I misunderstood. I thought 1G speed always requires
> autonegotiation. And phy_support_sym_pause would display that the
> only pause supported by this MAC is symmetric. But what you are
> saying is that we don't really "negotiate" the pause since our MAC
> HW supports only symmetric pause?

The point of negotiation is that the link peer can say it does not
support pause, because it is missing the needed hardware, or because
of a policy decision. Pause can be bad, particularly if used away from
the leaf nodes of the network. If the negotiation says pause should
not be used, you really should not use it.

Now, you hardware seems to be very limited. You cannot turn pause
off. It is hard coded on. So you cannot negotiate this feature. You
need to report that in ethtool. And you are also going to have to
manually configure pause in the link peer. Since it cannot be
negotiated, the peer is not going to use pause. Meaning by default,
pause in your MAC is pointless. You need to manually configure pause
in the link peer, by telling it to also not to negotiate, and perform
fixed symmetric pause.

Hopefully for the next generation of the hardware, you can fix this
bad design decision.

	Andrew

      reply	other threads:[~2021-06-01 14:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 19:37 [PATCH net-next v5] Add Mellanox BlueField Gigabit Ethernet driver David Thompson
2021-05-28 22:14 ` Jakub Kicinski
2021-06-01  1:10   ` David Thompson
2021-05-29  0:22 ` Andrew Lunn
2021-06-01 12:48   ` Asmaa Mnebhi
2021-06-01 13:19     ` Andrew Lunn
2021-06-01 13:43       ` Asmaa Mnebhi
2021-06-01 14:12         ` Andrew Lunn [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=YLZATclYESd9ROcd@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=asmaa@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=davthompson@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=limings@nvidia.com \
    --cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.