From: David Ahern <dsahern@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
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: Tue, 19 Aug 2025 09:27:14 -0600 [thread overview]
Message-ID: <8b801c6c-ee90-41ec-88dc-0b57b7bb7ca2@gmail.com> (raw)
In-Reply-To: <20250818090010.1201f52a@kernel.org>
On 8/18/25 10:00 AM, Jakub Kicinski wrote:
> 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".
kind of hard to answer that without some proposal with details on what
an integration of ynl would look like
next prev parent reply other threads:[~2025-08-19 15:27 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
2025-08-19 15:27 ` David Ahern [this message]
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=8b801c6c-ee90-41ec-88dc-0b57b7bb7ca2@gmail.com \
--to=dsahern@gmail.com \
--cc=dipayanroy@microsoft.com \
--cc=ernis@linux.microsoft.com \
--cc=ernis@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kuba@kernel.org \
--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.