[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3f0e780f-9660-93d0-9c84-cc81727cd3b6@intel.com>
Date: Tue, 18 Oct 2022 17:13:03 +0200
From: "Wilczynski, Michal" <michal.wilczynski@...el.com>
To: Jiri Pirko <jiri@...nulli.us>
CC: <netdev@...r.kernel.org>, <alexandr.lobakin@...el.com>,
<jacob.e.keller@...el.com>, <jesse.brandeburg@...el.com>,
<przemyslaw.kitszel@...el.com>, <anthony.l.nguyen@...el.com>,
<kuba@...nel.org>, <ecree.xilinx@...il.com>
Subject: Re: [PATCH net-next v6 0/4] Implement devlink-rate API and extend it
On 10/18/2022 4:16 PM, Jiri Pirko wrote:
> Tue, Oct 18, 2022 at 02:35:38PM CEST, michal.wilczynski@...el.com wrote:
>> This is a follow up on:
>> https://lore.kernel.org/netdev/20220915134239.1935604-1-michal.wilczynski@intel.com/
>>
>> This patch series implements devlink-rate for ice driver. Unfortunately
>> current API isn't flexible enough for our use case, so there is a need to
>> extend it. Some functions have been introduced to enable the driver to
>> export current Tx scheduling configuration.
> This is not enough to be said in the cover letter. You need to clearly
> explain the motivation, what is the problem you are trying to solve and
> describe the solution. Also, provide example commands and outputs here.
Sure I will update the cover letter.
Maybe I'll paste some info from the third commit of this patch series.
It contains examples and more justification. Didn't want to
duplicate this, but maybe it'll help.
Thanks,
MichaĆ
Powered by blists - more mailing lists