[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <13fe03dd-9454-fbbb-775a-083e0bf85bad@intel.com>
Date: Wed, 23 Aug 2023 14:39:23 -0700
From: "Zhang, Xuejun" <xuejun.zhang@...el.com>
To: Jiri Pirko <jiri@...nulli.us>, Jakub Kicinski <kuba@...nel.org>
CC: Wenjun Wu <wenjun1.wu@...el.com>, <intel-wired-lan@...ts.osuosl.org>,
<netdev@...r.kernel.org>, <madhu.chittim@...el.com>, <qi.z.zhang@...el.com>,
<anthony.l.nguyen@...el.com>
Subject: Re: [PATCH iwl-next v4 0/5] iavf: Add devlink and devlink rate
support'
On 8/22/2023 8:34 AM, Jiri Pirko wrote:
> Tue, Aug 22, 2023 at 05:12:55PM CEST, kuba@...nel.org wrote:
>> On Tue, 22 Aug 2023 08:12:28 +0200 Jiri Pirko wrote:
>>> NACK! Port function is there to configure the VF/SF from the eswitch
>>> side. Yet you use it for the configureation of the actual VF, which is
>>> clear misuse. Please don't
>> Stating where they are supposed to configure the rate would be helpful.
> TC?
Our implementation is an extension to this commit 42c2eb6b1f43 ice:
Implement devlink-rate API).
We are setting the Tx max & share rates of individual queues in a VF
using the devlink rate API.
Here we are using DEVLINK_PORT_FLAVOUR_VIRTUAL as the attribute for the
port to distinguish it from being eswitch.
[resend in plain text only]
Powered by blists - more mailing lists