From: Stephen Hemminger <stephen@networkplumber.org>
To: skakishi <skakishi@yahoo-corp.jp>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] Improving `ip link show` output in iproute2 for PF/VF association
Date: Wed, 20 Sep 2023 08:23:53 -0700 [thread overview]
Message-ID: <20230920082353.6a6cefcb@hermes.local> (raw)
In-Reply-To: <20230920052826.22211-1-skakishi@yahoo-corp.jp>
On Wed, 20 Sep 2023 14:28:27 +0900
skakishi <skakishi@yahoo-corp.jp> wrote:
> Hello all,
>
> The current version of iproute2 does not display clear associations between
> Physical Functions (PFs) and Virtual Functions (VFs). To address this limitation,
> I've added the following enhancement.
>
> Proposed Changes
> When the 'detail' option is enabled, the command will display additional details,
> including VF IDs and their respective names.
>
> For non-SR-IOV legacy mode:
> $ ip link show -d
> ...
> 1: enp6s0f0np0: ...
> vf 0 link/ether ... name enp6s0f1v0
> vf 1 link/ether ... name enp6s0f1v1
> ...
>
> For SR-IOV switchdev mode (including VF representor information):
> $ ip link show -d
> ...
> 1: enp6s0f0np0: ...
> vf 0 link/ether ... name enp6s0f0v0, representor enp6s0f0npf0vf0
> vf 1 link/ether ... name enp6s0f0v1, representor enp6s0f0npf0vf1
> ...
>
> Technical Details
> I've taken the additional data from sysfs.
>
> Current Work Status
> I am actively working on implementing this extension.
>
> Request for Feedback
> Do you find this feature useful?
> Do you think getting data from sysfs is an appropriate approach? Are there any
> alternative methods you would recommend?
>
> Best regards,
I prefer that functionality in iproute2 comes from netlink.
The kernel may need a change to put the vfinfo in the current netlink data.
Sysfs becomes less likely to work in cases where containers or other security parameters
are involved.
prev parent reply other threads:[~2023-09-20 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 5:28 [PATCH net-next] Improving `ip link show` output in iproute2 for PF/VF association skakishi
2023-09-20 15:23 ` Stephen Hemminger [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=20230920082353.6a6cefcb@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=skakishi@yahoo-corp.jp \
/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).