On 29.05.2024 02:02, Jacob Keller wrote:
>
>
> On 5/28/2024 12:16 PM, Jakub Kicinski wrote:
>> On Tue, 28 May 2024 13:01:32 +0200 Wojciech Drewek wrote:
>>> Subject: [PATCH iwl-net v2] ice: Add support for devlink loopback param.
>>
>> iwl-next, presumably
>>
>> Param makes sense, although the
On 5/28/2024 12:16 PM, Jakub Kicinski wrote:
> On Tue, 28 May 2024 13:01:32 +0200 Wojciech Drewek wrote:
>> Subject: [PATCH iwl-net v2] ice: Add support for devlink loopback param.
>
> iwl-next, presumably
>
> Param makes sense, although the name keeps giving me pause.
> I expect "loopback" wi
On Tue, 28 May 2024 13:01:32 +0200 Wojciech Drewek wrote:
> Subject: [PATCH iwl-net v2] ice: Add support for devlink loopback param.
iwl-next, presumably
Param makes sense, although the name keeps giving me pause.
I expect "loopback" will control either port loopback or something
like hairpin. W
On 5/28/2024 1:01 PM, Wojciech Drewek wrote:
From: Pawel Kaminski
Add support for driver-specific devlink loopback param. Supported values
are "enabled", "disabled" and "prioritized". Default configuration is
set to "enabled".
Add documentation in networking/devlink/ice.rst.
In previous ge
From: Pawel Kaminski
Add support for driver-specific devlink loopback param. Supported values
are "enabled", "disabled" and "prioritized". Default configuration is
set to "enabled".
Add documentation in networking/devlink/ice.rst.
In previous generations of Intel NICs the trasmit scheduler was