From: Stephen Hemminger <stephen@networkplumber.org>
To: Dekel Peled <dekelp@mellanox.com>
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: Mon, 4 Mar 2019 11:14:04 -0800 [thread overview]
Message-ID: <20190304111404.0225aa46@shemminger-XPS-13-9360> (raw)
In-Reply-To: <VI1PR05MB4224D48255BE41BE01174EB5B6700@VI1PR05MB4224.eurprd05.prod.outlook.com>
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.
next prev parent reply other threads:[~2019-03-04 19:14 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 [this message]
2019-03-05 8:46 ` Dekel Peled
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=20190304111404.0225aa46@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=orika@mellanox.com \
--cc=shahafs@mellanox.com \
--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).