From: Stephen Hemminger <stephen@networkplumber.org>
To: Erni Sri Satya Vennela <ernis@linux.microsoft.com>
Cc: dsahern@gmail.com, netdev@vger.kernel.org,
haiyangz@microsoft.com, shradhagupta@linux.microsoft.com,
ssengar@microsoft.com, dipayanroy@microsoft.com,
ernis@microsoft.com
Subject: Re: [PATCH iproute2-next v3] iproute2: Add 'netshaper' command to 'ip link' for netdev shaping
Date: Sat, 16 Aug 2025 15:55:10 -0700 [thread overview]
Message-ID: <20250816155510.03a99223@hermes.local> (raw)
In-Reply-To: <1754895902-8790-1-git-send-email-ernis@linux.microsoft.com>
On Mon, 11 Aug 2025 00:05:02 -0700
Erni Sri Satya Vennela <ernis@linux.microsoft.com> wrote:
> Add support for the netshaper Generic Netlink
> family to iproute2. Introduce a new subcommand to `ip link` for
> configuring netshaper parameters directly from userspace.
>
> This interface allows users to set shaping attributes (such as speed)
> which are passed to the kernel to perform the corresponding netshaper
> operation.
>
> Example usage:
> $ip link netshaper { set | get | delete } dev DEVNAME \
> handle scope SCOPE id ID \
> [ speed SPEED ]
The choice of ip link is awkward and doesn't match other options.
I can think of some better other choices:
1. netshaper could be a property of the device. But the choice of using genetlink
instead of regular ip netlink attributes makes this hard.
2. netshaper could be part of devlink. Since it is more targeted at hardware
device attributes.
3. netshaper could be a standalone command like bridge, dcb, devlink, rdma, tipc and vdpa.
What ever choice the command line options need to follow similar syntax to other iproute commands.
next prev parent reply other threads:[~2025-08-16 22:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 7:05 [PATCH iproute2-next v3] iproute2: Add 'netshaper' command to 'ip link' for netdev shaping Erni Sri Satya Vennela
2025-08-11 20:16 ` Haiyang Zhang
2025-08-16 18:05 ` Stephen Hemminger
2025-08-21 10:45 ` Erni Sri Satya Vennela
2025-08-16 22:55 ` Stephen Hemminger [this message]
2025-08-18 15:36 ` Jakub Kicinski
2025-08-18 15:41 ` David Ahern
2025-08-18 16:00 ` Jakub Kicinski
2025-08-19 15:27 ` David Ahern
2025-08-21 12:31 ` Erni Sri Satya Vennela
2025-08-21 11:06 ` Erni Sri Satya Vennela
2025-08-21 14:12 ` Jakub Kicinski
2025-08-24 13:40 ` Erni Sri Satya Vennela
2025-08-24 14:23 ` Stephen Hemminger
2025-08-25 15:52 ` Jakub Kicinski
2025-08-25 16:16 ` Stephen Hemminger
2025-09-01 5:47 ` Erni Sri Satya Vennela
2025-08-21 10:49 ` Erni Sri Satya Vennela
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=20250816155510.03a99223@hermes.local \
--to=stephen@networkplumber.org \
--cc=dipayanroy@microsoft.com \
--cc=dsahern@gmail.com \
--cc=ernis@linux.microsoft.com \
--cc=ernis@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=shradhagupta@linux.microsoft.com \
--cc=ssengar@microsoft.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.