[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221201085330.5c6cb642@kernel.org>
Date: Thu, 1 Dec 2022 08:53:30 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Michal Wilczynski <michal.wilczynski@...el.com>
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 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?
Powered by blists - more mailing lists