<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word"> <div class="WordSection1"> + <a href="mailto:systemd-devel@lists.freedesktop.org">systemd-devel@lists.freedesktop.org</a><o:p></o:p> + <a href="mailto:dimitri.ledkov@surgut.co.uk">dimitri.ledkov@surgut.co.uk</a><o:p></o:p> <o:p> </o:p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: Haiyang Zhang Sent: Tuesday, April 16, 2024 5:59 PM To: dimitri.ledkov@canonical.com Cc: Jack Aboutboul <jaboutboul@microsoft.com>; Sharath George John <sgeorgejohn@microsoft.com>; Luca Boccassi <Luca.Boccassi@microsoft.com>; Partha Sarangam <partha.sarangam@microsoft.com>; Paul Rosswurm <paulros@microsoft.com> Subject: Better systemd naming for Azure/MANA nic Importance: High<o:p></o:p> </div> </div> <o:p> </o:p> Hi Dimitri,<o:p></o:p> <o:p> </o:p> During the meeting a few months ago, you mentioned we cannot set “net.if_name=0” due to impact of other device naming... We have recently fixed the Physical slot number of MANA NICs, could you change the naming scheme as discussed last time? <o:p></o:p> <o:p> </o:p> Currently the domain number is part of the name (and Physical Slot + dev_port), e.g. enP30832s1, enP30832s1d1, enP30832s1d2… But domain number is long, and may not be the same on different VMs.<o:p></o:p> <o:p> </o:p> As discussed previously, we prefer a short name based on the VF “Physical Slot” + dev_port.<o:p></o:p> For VF the Physical Slot starts from 1, and increment by 1 for each additional VF device. (PF nic doesn’t have the Physical Slot number, so you can continue to use “0” there).<o:p></o:p> The dev_port starts from 0, and increment by 1 for each additional dev_port (NIC).<o:p></o:p> <o:p> </o:p> Here is the logic we hope to have in the systemd: If a NIC’s driver is “mana”, use this naming scheme:<o:p></o:p> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse"> <tbody> <tr> <td width="623" valign="top" style="width:467.5pt;border:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt"> <prefix><Physical Slot>d<dev_port><o:p></o:p> <o:p> </o:p> //During the meeting, we briefly talked about the prefix can be “enm” (enthernet, mana), so the names of two VF devices with 3 dev_ports (NICs) each, can be:<o:p></o:p> <o:p> </o:p> enm1 // omits the dev_port number if it’s 0.<o:p></o:p> enm1d1<o:p></o:p> enm1d2<o:p></o:p> <o:p> </o:p> enm2 <o:p> </o:p> enm2d1<o:p></o:p> enm2d2<o:p></o:p> <o:p> </o:p> </td> </tr> </tbody> </table> <o:p> </o:p> <o:p> </o:p> Here is the Physical Slot, dev_port info from a running VM:<o:p></o:p> root@lisa--500-e0-n1:/sys/class/net# lspci -v -s7870:00:00.0<o:p></o:p> 7870:00:00.0 Ethernet controller: Microsoft Corporation Device 00ba<o:p></o:p> Subsystem: Microsoft Corporation Device 00b9<o:p></o:p> Physical Slot: 1<o:p></o:p> Flags: bus master, fast devsel, latency 0, NUMA node 0<o:p></o:p> Memory at fc2000000 (64-bit, prefetchable) [size=32M]<o:p></o:p> Memory at fc4000000 (64-bit, prefetchable) [size=32K]<o:p></o:p> Capabilities: [70] Express Endpoint, MSI 00<o:p></o:p> Capabilities: [b0] MSI-X: Enable+ Count=1024 Masked-<o:p></o:p> Capabilities: [100] Alternative Routing-ID Interpretation (ARI)<o:p></o:p> Kernel driver in use: mana<o:p></o:p> <o:p> </o:p> root@lisa--500-e0-n1:/sys/class/net# grep "" en*/dev_port<o:p></o:p> enP30832s1/dev_port:0<o:p></o:p> enP30832s1d1/dev_port:1<o:p></o:p> enP30832s1d2/dev_port:2<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> <ul style="margin-top:0in" type="disc"> <li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3">Haiyang<o:p></o:p></li></ul> <o:p> </o:p> </div> </div> </body> </html>