From: Kevin Traynor <ktraynor@redhat.com>
To: Viacheslav Ovsiienko <viacheslavo@mellanox.com>, stable@dpdk.org
Cc: Ali Alnubani <alialnu@mellanox.com>
Subject: Re: [dpdk-stable] [PATCH] [18.11] net/mlx5: fix mlx5 devices port naming
Date: Fri, 3 Jul 2020 11:27:03 +0100 [thread overview]
Message-ID: <b6029a16-4245-2e8d-5095-8ba1481d06de@redhat.com> (raw)
In-Reply-To: <1593700670-25730-1-git-send-email-viacheslavo@mellanox.com>
On 02/07/2020 15:37, Viacheslav Ovsiienko wrote:
> The newer kernel changed the physical port naming for mlx5 devices.
> This patch provides the integrated support for new naming recognition.
>
> The following port naming formats are supported:
>
> - missing physical port name (no sysfs/netlink key) at all,
> master is assumed
>
> - decimal digits (for example "12"), representor is
> assumed, the value is the index of attached VF
>
> - "p" followed by decimal digits, for example "p2", master
> is assumed
>
> Switchdev mode (representors and master) are recognized and
> supported only for older kernels (<= 4.19) and OFED <= 4.4,
> without multiport IB device support. Adding the multiport
> IB device support would require adding the entire feature
> and shared context approach would be introduced.
>
> Fixes: 26c08b979d26 ("net/mlx5: add port representor awareness")
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Added Reported tags and applied. Thanks Ali for finding this issue and
Slava for fixing it.
prev parent reply other threads:[~2020-07-03 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 14:37 Viacheslav Ovsiienko
2020-07-03 10:27 ` Kevin Traynor [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=b6029a16-4245-2e8d-5095-8ba1481d06de@redhat.com \
--to=ktraynor@redhat.com \
--cc=alialnu@mellanox.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@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).