From: Ido Schimmel <idosch@mellanox.com>
To: Saeed Mahameed <saeedm@dev.mellanox.co.il>
Cc: Saeed Mahameed <saeedm@mellanox.com>,
"David S. Miller" <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
Or Gerlitz <ogerlitz@mellanox.com>, Tal Alon <talal@mellanox.com>,
Eran Ben Elisha <eranbe@mellanox.com>,
Eugenia Emantayev <eugenia@mellanox.com>,
Jiri Pirko <jiri@mellanox.com>, <eladr@mellanox.com>
Subject: Re: [PATCH net-next 12/12] net/mlx5e: Disable link up on INIT HCA command
Date: Sun, 24 Apr 2016 01:03:59 +0300 [thread overview]
Message-ID: <20160423220359.GA2841@colbert.idosch.org> (raw)
In-Reply-To: <CALzJLG-AWFHnba=ysCAQLqCjFHo3L-sQTeW+NbpMg-X6PRtRPQ@mail.gmail.com>
Sat, Apr 23, 2016 at 11:21:45PM IDT, saeedm@dev.mellanox.co.il wrote:
>On Sat, Apr 23, 2016 at 7:00 PM, Ido Schimmel <idosch@mellanox.com> wrote:
>> mutt suggests I sent you the following patches a while ago:
>>
>> net/mlx5e: Set port administrative status in ndo_{open, close}
>> net/mlx5e: Initialize port administrative status to down
>>
>> So I'm curious as to why you didn't follow up on them and instead came
>> up with this patch.
>>
>> When I initially debugged this I pointed you to the fact that the
>> firmware also needs to be patched, as setting the administrative status
>> down via PAOS doesn't really do anything. The operational status will
>> remain up. I just tested this patchset with the latest release firmware
>> (12.14.2036) and I'm bumping into the same problem.
>>
>
>Hi Ido,
>
>I do remember that patch, and back then i told you that your patch is
>not cooked enough and that we were working on a solution:
>
>1. you need to negotiate with the FW on if the FW can give up port
>ownership to SW, you can find that in handle_hca_cap,
>MLX5_CAP_GEN_MAX(dev, disable_link_up).
Yea, I don't think that part was available back then? I just directly
set a value in firmware memory hoping it would be the default in the
next version following my report.
>2. you need to configure the FW to give up port ownership via NVconfig
>(mlxconfig tool) i think it is PORT_OWNER bit, Eran can elaborate
>more if needed.
I'll check that tomorrow morning and report.
>3.1 and 2 are required for mlx5_set_port_admin_status to take effect,
>otherwise it is a NOOP.
>
>Eran tested this patch and it works for him, maybe you missed step 2.
>Step 2 will not be required in future FW (it will be the FW default).
Great!
>Other than this patch, nothing more is required for driver to assume
>ownership on port's link status.
>
>> Until this is properly fixed the mlx5 driver is blacklisted in our test:
>> https://github.com/jpirko/lnst/blob/master/recipes/switchdev/basic-001-links.py#L19
>>
>> Also, why is this directed at net-next?
>>
>
>it is kind of new behavior, and not a bug fix.
>
>>> drivers/infiniband/hw/mlx5/main.c | 11 +++++++++++
>>> drivers/infiniband/hw/mlx5/mlx5_ib.h | 5 +++++
>>> drivers/net/ethernet/mellanox/mlx5/core/en_dcbnl.c | 4 ++--
>>> .../net/ethernet/mellanox/mlx5/core/en_ethtool.c | 4 ++--
>>> drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 4 ++++
>>> drivers/net/ethernet/mellanox/mlx5/core/main.c | 4 ++++
>>> drivers/net/ethernet/mellanox/mlx5/core/port.c | 5 +++--
>>> include/linux/mlx5/port.h | 3 ++-
>>> 8 files changed, 33 insertions(+), 7 deletions(-)
>>>
>>
>> [...]
>>
>>>diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_dcbnl.c b/drivers/net/ethernet/mellanox/mlx5/core/en_dcbnl.c
>>>index b2db180..f083797 100644
>>>--- a/drivers/net/ethernet/mellanox/mlx5/core/en_dcbnl.c
>>>+++ b/drivers/net/ethernet/mellanox/mlx5/core/en_dcbnl.c
>>>@@ -202,12 +202,12 @@ static int mlx5e_dcbnl_ieee_setpfc(struct net_device *dev,
>>>
>>> mlx5_query_port_admin_status(mdev, &ps);
>>> if (ps == MLX5_PORT_UP)
>>>- mlx5_set_port_admin_status(mdev, MLX5_PORT_DOWN);
>>>+ mlx5_set_port_admin_status(mdev, MLX5_PORT_DOWN, 1);
>>
>> Why is this needed? The link doesn't need to go through training when
>> setting PFC. It's only needed for PAUSE frames when auto-negotiation is
>> on, but you don't support that anyway.
>>
>> Thanks.
>>
>
>The code was there before this patch, only the function prototype was changed.
>Maybe you have a valid point here, but this need to be fixed in a
>different patch, it has nothing to do with this one.
>Eran and Team please check this on Sunday, I found nothing re this
>matter in PRM.
See PFCC register:
"Setting pfctx / pfcrx when the link is up takes effect immediately."
Thanks.
prev parent reply other threads:[~2016-04-23 22:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 19:00 [PATCH net-next 00/12] Mellanox 100G extending mlx5 ethtool support Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 01/12] net/mlx5e: Report additional error statistics in get stats ndo Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 02/12] net/mlx5e: Statistics handling refactoring Saeed Mahameed
2016-04-25 10:58 ` David Laight
2016-04-25 12:12 ` Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 03/12] net/mlx5e: Rename VPort counters Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 04/12] net/mlx5e: Add per priority group to PPort counters Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 05/12] net/mlx5e: Add link down events counter Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 06/12] net/mlx5e: Improve set features ndo resiliency Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 07/12] net/mlx5e: Add support for RXALL netdev feature Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 08/12] net/mlx5e: Add ethtool support for interface identify (LED blinking) Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 09/12] net/mlx5e: Add ethtool support for dump module EEPROM Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 10/12] net/mlx5e: Add ethtool support for rxvlan-offload (vlan stripping) Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 11/12] net/mlx5e: Fix checksum handling for non-stripped vlan packets Saeed Mahameed
2016-04-22 19:00 ` [PATCH net-next 12/12] net/mlx5e: Disable link up on INIT HCA command Saeed Mahameed
2016-04-23 16:00 ` Ido Schimmel
2016-04-23 20:21 ` Saeed Mahameed
2016-04-23 20:28 ` Or Gerlitz
2016-04-23 21:24 ` Saeed Mahameed
2016-04-23 21:28 ` Or Gerlitz
2016-04-23 22:03 ` Ido Schimmel [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=20160423220359.GA2841@colbert.idosch.org \
--to=idosch@mellanox.com \
--cc=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=eranbe@mellanox.com \
--cc=eugenia@mellanox.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=saeedm@dev.mellanox.co.il \
--cc=saeedm@mellanox.com \
--cc=talal@mellanox.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).