[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220922055040.7c869e9c@kernel.org>
Date: Thu, 22 Sep 2022 05:50:40 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Wilczynski, Michal" <michal.wilczynski@...el.com>
Cc: Edward Cree <ecree.xilinx@...il.com>, <netdev@...r.kernel.org>,
<alexandr.lobakin@...el.com>, <dchumak@...dia.com>,
<maximmi@...dia.com>, <jiri@...nulli.us>,
<simon.horman@...igine.com>, <jacob.e.keller@...el.com>,
<jesse.brandeburg@...el.com>, <przemyslaw.kitszel@...el.com>
Subject: Re: [RFC PATCH net-next v4 2/6] devlink: Extend devlink-rate api
with queues and new parameters
On Thu, 22 Sep 2022 13:44:14 +0200 Wilczynski, Michal wrote:
> Below I'll paste the output of how initially the topology looks like for our
> hardware.
> If the devlink_port objects are present (as in switchdev mode), there
> should also be vport nodes represented. It is NOT a requirement for
> a queue to have a vport as it's ancestor.
Thanks! How did you know that my preferred method of reading
hierarchies is looking at a linear output!? 😕
Anyway. My gut feeling is that this is cutting a corner. Seems
most natural for the VF/PF level to be controlled by the admin
and the queue level by whoever owns the queue. The hypervisor
driver/FW should reconcile the two and compile the full hierarchy.
Powered by blists - more mailing lists