[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <24bca169-1f7b-4034-9893-5cd1f1c0ad1b@intel.com>
Date: Mon, 5 Dec 2022 09:41:26 +0100
From: "Wilczynski, Michal" <michal.wilczynski@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: <netdev@...r.kernel.org>, <alexandr.lobakin@...el.com>,
<przemyslaw.kitszel@...el.com>, <jiri@...nulli.us>,
<wojciech.drewek@...el.com>, <dsahern@...il.com>,
<stephen@...workplumber.org>
Subject: Re: [PATCH iproute2-next v2 0/4] Implement new netlink attributes for
devlink-rate in iproute2
On 12/1/2022 5:53 PM, Jakub Kicinski wrote:
> On Thu, 1 Dec 2022 11:26:22 +0100 Michal Wilczynski wrote:
>> Patch implementing new netlink attributes for devlink-rate got merged to
>> net-next.
>> https://lore.kernel.org/netdev/20221115104825.172668-1-michal.wilczynski@intel.com/
>>
>> Now there is a need to support these new attributes in the userspace
>> tool. Implement tx_priority and tx_weight in devlink userspace tool. Update
>> documentation.
> I forgot to ask you - is there anything worth adding to the netdevsim
> rate selftests to make sure devlink refactoring doesn't break your use
> case? Probably the ability for the driver to create and destroy the
> hierarchy?
Hi,
I think it's a great idea, possibility to export the hierarchy from the driver
is key for our use case. Would you like me to add this to netdevism ?
Thanks,
MichaĆ
Powered by blists - more mailing lists