From: Jakub Kicinski <kuba@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Erni Sri Satya Vennela <ernis@linux.microsoft.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: Mon, 18 Aug 2025 09:00:10 -0700 [thread overview]
Message-ID: <20250818090010.1201f52a@kernel.org> (raw)
In-Reply-To: <31e038a1-5a17-4c13-bf37-d07cbccd7056@gmail.com>
On Mon, 18 Aug 2025 09:41:29 -0600 David Ahern wrote:
> On 8/18/25 9:36 AM, Jakub Kicinski wrote:
> > Somewhat related -- what's your take on integrating / vendoring in YNL?
>
> I feel like this has been brought up a few times.
>
> Is there a specific proposal or any patches to review?
Not AFAIK. Erni is being asked to rethink his approach here, and
if we're going with a new command perhaps YNL should be on the table.
I'd be very interested to get a final ruling on YNL integration
into iproute2 -- given its inability to work as a shared object /
library it's not unreasonable for the answer to be "no".
The page pool sample in the kernel sources is very useful, I find
myself copying to various systems during debug. If there's no clear
path to YNL integration with iproute2 it's time for that sample to
be come a real CLI tool.
next prev parent reply other threads:[~2025-08-18 16:00 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
2025-08-18 15:36 ` Jakub Kicinski
2025-08-18 15:41 ` David Ahern
2025-08-18 16:00 ` Jakub Kicinski [this message]
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=20250818090010.1201f52a@kernel.org \
--to=kuba@kernel.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 \
--cc=stephen@networkplumber.org \
/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.