Re: [Intel-wired-lan] [PATCH iwl-next v5 15/15] ixd: add devlink support

[Jacob Keller]

On 11/17/2025 6:28 AM, Loktionov, Aleksandr wrote:
> 
> 
>> -----Original Message-----
>> From: Intel-wired-lan <intel-wired-lan-bounces@xxxxxxxxxx> On Behalf
>> Of Larysa Zaremba
>> Sent: Monday, November 17, 2025 2:49 PM
>> To: intel-wired-lan@xxxxxxxxxxxxxxxx; Nguyen, Anthony L
>> <anthony.l.nguyen@xxxxxxxxx>
>> Cc: Lobakin, Aleksander <aleksander.lobakin@xxxxxxxxx>; Samudrala,
>> Sridhar <sridhar.samudrala@xxxxxxxxx>; Singhai, Anjali
>> <anjali.singhai@xxxxxxxxx>; Michal Swiatkowski
>> <michal.swiatkowski@xxxxxxxxxxxxxxx>; Zaremba, Larysa
>> <larysa.zaremba@xxxxxxxxx>; Fijalkowski, Maciej
>> <maciej.fijalkowski@xxxxxxxxx>; Tantilov, Emil S
>> <emil.s.tantilov@xxxxxxxxx>; Chittim, Madhu <madhu.chittim@xxxxxxxxx>;
>> Hay, Joshua A <joshua.a.hay@xxxxxxxxx>; Keller, Jacob E
>> <jacob.e.keller@xxxxxxxxx>; Shanmugam, Jayaprakash
>> <jayaprakash.shanmugam@xxxxxxxxx>; Wochtman, Natalia
>> <natalia.wochtman@xxxxxxxxx>; Jiri Pirko <jiri@xxxxxxxxxxx>; David S.
>> Miller <davem@xxxxxxxxxxxxx>; Eric Dumazet <edumazet@xxxxxxxxxx>;
>> Jakub Kicinski <kuba@xxxxxxxxxx>; Paolo Abeni <pabeni@xxxxxxxxxx>;
>> Simon Horman <horms@xxxxxxxxxx>; Jonathan Corbet <corbet@xxxxxxx>;
>> Richard Cochran <richardcochran@xxxxxxxxx>; Kitszel, Przemyslaw
>> <przemyslaw.kitszel@xxxxxxxxx>; Andrew Lunn <andrew+netdev@xxxxxxx>;
>> netdev@xxxxxxxxxxxxxxx; linux-doc@xxxxxxxxxxxxxxx; linux-
>> kernel@xxxxxxxxxxxxxxx
>> Subject: [Intel-wired-lan] [PATCH iwl-next v5 15/15] ixd: add devlink
>> support
>>
>> From: Amritha Nambiar <amritha.nambiar@xxxxxxxxx>
>>
>> Enable initial support for the devlink interface with the ixd driver.
>> The ixd hardware is a single function PCIe device. So, the PCIe
>> adapter gets its own devlink instance to manage device-wide resources
>> or configuration.
>>
>> $ devlink dev show
>> pci/0000:83:00.6
>>
>> $ devlink dev info pci/0000:83:00.6
>> pci/0000:83:00.6:
>>   driver ixd
>>   serial_number 00-a0-c9-ff-ff-23-45-67
>>   versions:
>>       fixed:
>>         device.type MEV
>>       running:
>>         cp 0.0
>>         virtchnl 2.0
>>
> This commit mentions MEV without expansion.
> Kernel docs require expanding uncommon abbreviations.
> 

This is an example of the output of devlink, so if devlink literally
does print MEV, this should stay as-is. You could provide an area which
explains what each device type means and has the expanded definition.

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature