From: Dekel Peled <dekelp@mellanox.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Shahaf Shuler <shahafs@mellanox.com>,
Yongseok Koh <yskoh@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>,
Ori Kam <orika@mellanox.com>, Matan Azrad <matan@mellanox.com>
Subject: Re: [dpdk-dev] [RFC v2] net/mlx5: support new naming scheme for representors
Date: Tue, 5 Mar 2019 08:46:26 +0000 [thread overview]
Message-ID: <VI1PR05MB4224ED4F64BB2F631D227A31B6720@VI1PR05MB4224.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20190304111404.0225aa46@shemminger-XPS-13-9360>
Thanks, PSB.
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Monday, March 4, 2019 9:14 PM
> To: Dekel Peled <dekelp@mellanox.com>
> Cc: Shahaf Shuler <shahafs@mellanox.com>; Yongseok Koh
> <yskoh@mellanox.com>; dev@dpdk.org; Ori Kam <orika@mellanox.com>;
> Matan Azrad <matan@mellanox.com>
> Subject: Re: [dpdk-dev] [RFC v2] net/mlx5: support new naming scheme for
> representors
>
> On Sun, 3 Mar 2019 07:14:07 +0000
> Dekel Peled <dekelp@mellanox.com> wrote:
>
> > In current kernel implementation, the physical port name for representors
> is a numeric string (i.e. '0', '1', etc.).
> >
> >
> >
> > Kernel patch [1] implements an updated scheme for naming of
> representors ports.
> >
> > The new scheme gives a unique name for each port using the PF ID and the
> VF ID.
> >
> > Uplink representors are named 'p0', 'p1', etc.
> >
> > VF representors are named 'pf0vf0', 'pf0vf1', 'pf1vf0', 'pf1vf1', etc.
>
>
> Depending on kernel to use any particular naming policy is going to be
> problematic.
> Users will want to run on older kernels, and many distributions rename
> interfaces through udev or other mechanism.
MLX5 PMD relies on specific kernel implementation, with known scheme for representor naming.
Users running older kernels are required to install MLNX OFED, which implements the naming scheme expected by MLX5 PMD.
prev parent reply other threads:[~2019-03-05 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 7:14 Dekel Peled
2019-03-04 19:14 ` Stephen Hemminger
2019-03-05 8:46 ` Dekel Peled [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=VI1PR05MB4224ED4F64BB2F631D227A31B6720@VI1PR05MB4224.eurprd05.prod.outlook.com \
--to=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=orika@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=yskoh@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).