From: Stephen Hemminger <stephen@networkplumber.org>
To: renmingshuai <renmingshuai@huawei.com>
Cc: <netdev@vger.kernel.org>, <dsahern@gmail.com>, <yanan@huawei.com>,
<liaichun@huawei.com>
Subject: Re: [PATCH] iplink: add an option to set IFLA_EXT_MASK attribute
Date: Wed, 3 Apr 2024 17:35:27 -0700 [thread overview]
Message-ID: <20240403173527.63266cc5@hermes.local> (raw)
In-Reply-To: <20240403032021.29899-1-renmingshuai@huawei.com>
On Wed, 3 Apr 2024 11:20:21 +0800
renmingshuai <renmingshuai@huawei.com> wrote:
> Kernel has add IFLA_EXT_MASK attribute for indicating that certain
> extended ifinfo values are requested by the user application. The ip
> link show cmd always request VFs extended ifinfo.
>
> RTM_GETLINK for greater than about 220 VFs truncates IFLA_VFINFO_LIST
> due to the maximum reach of nlattr's nla_len being exceeded.
> As a result, ip link show command only show the truncated VFs info sucn as:
>
> #ip link show dev eth0
> 1: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 ...
> link/ether ...
> vf 0 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff ...
> Truncated VF list: eth0
>
> Add an option to set IFLA_EXT_MASK attribute and users can choose to
> show the extended ifinfo or not.
>
> Signed-off-by: Mingshuai Ren <renmingshuai@huawei.com>
Adding a new option with on/off seems like more than is necessary.
If we need an option it should just be one word. Any new filter should
have same conventions as existing filters. Maybe 'novf'
And it looks like not sending IFLA_EXT_MASK will break the changes
made for the link filter already done for VF's.
next prev parent reply other threads:[~2024-04-04 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 3:20 [PATCH] iplink: add an option to set IFLA_EXT_MASK attribute renmingshuai
2024-04-04 0:35 ` Stephen Hemminger [this message]
2024-04-08 12:34 ` renmingshuai
2024-04-09 0:29 ` Stephen Hemminger
2024-04-09 1:53 ` renmingshuai
2024-04-09 14:47 ` David Ahern
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=20240403173527.63266cc5@hermes.local \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=liaichun@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=renmingshuai@huawei.com \
--cc=yanan@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.