From: "Wilczynski, Michal" <michal.wilczynski@intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next v4 3/3] ice: Enable switching default tx scheduler topology
Date: Wed, 20 Jul 2022 16:48:56 +0200 [thread overview]
Message-ID: <8204d5fd-9f5b-1d32-4bf1-c13dbbfe478b@intel.com> (raw)
In-Reply-To: <4cc6a468-1ff9-a894-543a-7baa29500aa2@intel.com>
Hi,
I created a new version that includes Lukasz commit with devlink param
implementation.
Thanks,
Michał
On 7/14/2022 10:31 PM, Tony Nguyen wrote:
>
>
> On 7/12/2022 12:51 AM, Wilczynski, Michal wrote:
>>
>>
>> On 7/12/2022 2:25 AM, Tony Nguyen wrote:
>>>
>>>
>>> On 7/4/2022 5:32 AM, Michal Wilczynski wrote:
>>>> Introduce support for tx scheduler topology change, based on user
>>>> selection, from default 9-layer to 5-layer. In order for switch to be
>>>> successful there is a new NVM(version 3.20 or older) and DDP
>>>> package(OS
>>>> Package 1.3.29 or older).
>>>>
>>>> Enable 5-layer topology switch in init path of the driver. To
>>>> accomplish
>>>> that upload of the DDP package needs to be delayed, until change in Tx
>>>> topology is finished. To trigger the Tx change user selection
>>>> should be
>>>> changed in NVM using devlink. Then the platform should be rebooted.
>>>>
>>>> Example way of switching NVM settings in devlink:
>>>>
>>>> Show:
>>>> devlink dev param show pci/0000:4b:00.0
>>>> name txbalancing type driver-specific
>>>> values:
>>>> cmode permanent value true
>>>>
>>>> Set:
>>>> devlink dev param set pci/0000:4b:00.0 name txbalancing value true
>>>> cmode
>>>> permanent
>>>
>>> Did I miss the devlink implementation?
>>
>> It's not upstreamed yet, however I had to provide some example on how
>> this might be
>> configured. There was a review comment about that. I tested it by
>> using epct with OOT
>> driver first. Obviously I can't provide this method for upstream
>> community.
>
> As there is a plan to send the devlink implementation soon, these
> should all be put together into a series that has the functionality as
> well as the ability to get/set it. If it is too large for a series,
> provide some method to view the other portions of code such as RFC
> patches or point to a repo that contains it.
>
> I don't believe functionality that would, currently, require
> installing the OOT driver to change modes is acceptable.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2022-07-20 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 12:32 [Intel-wired-lan] [PATCH net-next v3 0/3] ice: Support 5 layer tx scheduler topology Michal Wilczynski
2022-07-04 12:32 ` [Intel-wired-lan] [PATCH net-next v4 1/3] ice: Support 5 layer topology Michal Wilczynski
2022-07-04 12:32 ` [Intel-wired-lan] [PATCH net-next v4 2/3] ice: Adjust the VSI/Aggregator layers Michal Wilczynski
2022-07-04 12:32 ` [Intel-wired-lan] [PATCH net-next v4 3/3] ice: Enable switching default tx scheduler topology Michal Wilczynski
2022-07-12 0:25 ` Tony Nguyen
2022-07-12 7:51 ` Wilczynski, Michal
2022-07-14 20:31 ` Tony Nguyen
2022-07-20 14:48 ` Wilczynski, Michal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8204d5fd-9f5b-1d32-4bf1-c13dbbfe478b@intel.com \
--to=michal.wilczynski@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox