[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250818090010.1201f52a@kernel.org>
Date: Mon, 18 Aug 2025 09:00:10 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: David Ahern <dsahern@...il.com>
Cc: Stephen Hemminger <stephen@...workplumber.org>, Erni Sri Satya Vennela
<ernis@...ux.microsoft.com>, netdev@...r.kernel.org,
haiyangz@...rosoft.com, shradhagupta@...ux.microsoft.com,
ssengar@...rosoft.com, dipayanroy@...rosoft.com, ernis@...rosoft.com
Subject: Re: [PATCH iproute2-next v3] iproute2: Add 'netshaper' command to
'ip link' for netdev shaping
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.
Powered by blists - more mailing lists