[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231122192201.245a0797@kernel.org>
Date: Wed, 22 Nov 2023 19:22:01 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: "Zhang, Xuejun" <xuejun.zhang@...el.com>
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 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.
Powered by blists - more mailing lists