netdev - Re: [Intel-wired-lan] [PATCH iwl-next v4 0/5] iavf: Add devlink and devlink rate support'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e662dca5-84e4-4f7b-bfa3-50bce30c697c@intel.com>
Date: Mon, 27 Nov 2023 16:15:47 -0800
From: "Zhang, Xuejun" <xuejun.zhang@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: Jiri Pirko <jiri@...nulli.us>, <netdev@...r.kernel.org>,
	<anthony.l.nguyen@...el.com>, <intel-wired-lan@...ts.osuosl.org>,
	<qi.z.zhang@...el.com>, Wenjun Wu <wenjun1.wu@...el.com>,
	<maxtram95@...il.com>, "Chittim, Madhu" <madhu.chittim@...el.com>,
	"Samudrala, Sridhar" <sridhar.samudrala@...el.com>, <pabeni@...hat.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v4 0/5] iavf: Add devlink and
 devlink rate support'


On 11/22/2023 7:22 PM, Jakub Kicinski wrote:
> On Wed, 22 Nov 2023 14:19:14 -0800 Zhang, Xuejun wrote:
>> The proposed API would incur net/core and driver changes as follows
>> a) existing drivers with ndo_set_tx_maxrate support upgraded to use new
>> ndo_set_tx_rate
>> b) net sysfs (replacing ndo_set_maxrate with ndo_set_tx_rate with
>> minrate and burst set to 0, -1 means ignore)
>> c) Keep the existing /sys/class/net/ethx/queues/tx_nn/tx_maxrate as it
>> is currently
>> d) Add sysfs entry as /sys/class/net/ethx/queues/tx_nn/tx_minrate &
>> /sys/class/net/ethx/queues/tx_nn/burst
> You described extending the sysfs API (which the ndo you mention
> is for) and nothing about converging the other existing APIs.
This is extension of ndo_set_tx_maxrate to include per queue parameters 
of tx_minrate and burst.

devlink rate api includes tx_maxrate and tx_minrate, it is intended for 
port rate configurations.

With regarding to tc mqprio, it is being used to configure queue group 
per tc.

For sriov ndo ndo_set_vf_rate, that has been used for overall VF rate 
configuration, not for queue based rate configuration.

It seems there are differences on intent of the aforementioned APIs.

Our use case here is to allow user (i.e @ uAPI) to configure tx rates of 
max rate & min rate per VF queue.Hence we are inclined to 
ndo_set_tx_maxrate extension.