From: Jakub Kicinski <kuba@kernel.org>
To: Calvin Owens <calvin@wbinvd.org>
Cc: Ivan Vecera <ivecera@redhat.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
linux-kernel@vger.kernel.org,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH net] i40e: Prevent unwanted interface name changes
Date: Fri, 22 Aug 2025 07:23:26 -0700 [thread overview]
Message-ID: <20250822072326.725475ef@kernel.org> (raw)
In-Reply-To: <aKfwuFXnvOzWx5De@mozart.vkv.me>
On Thu, 21 Aug 2025 21:23:20 -0700 Calvin Owens wrote:
> > > If you actually have data on that, obviously that's different. But it
> > > sounds like you're guessing just like I am.
> >
> > I could only guess about other OS Vendors, one could check it also
> > for Ubuntu in their public git, but I don't think we need more data, as
> > ultimate judge here are Stable Maintainers
>
> Maybe I'm barking up the wrong tree, it's udev after all that decides to
> read the thing in /sys and name the interfaces differently because it's
> there...
Yeah, that's my feeling. Ideally there should be a systemd-networkd
setting that let's user opt out of adding the phys_port_name on
interfaces. 99% of users will not benefit from these, new drivers or
old. We're kinda making everyone suffer for the 1% :(
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Calvin Owens <calvin@wbinvd.org>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Michal Schmidt <mschmidt@redhat.com>,
netdev@vger.kernel.org, Tony Nguyen <anthony.l.nguyen@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>,
Ivan Vecera <ivecera@redhat.com>,
intel-wired-lan@lists.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] i40e: Prevent unwanted interface name changes
Date: Fri, 22 Aug 2025 07:23:26 -0700 [thread overview]
Message-ID: <20250822072326.725475ef@kernel.org> (raw)
In-Reply-To: <aKfwuFXnvOzWx5De@mozart.vkv.me>
On Thu, 21 Aug 2025 21:23:20 -0700 Calvin Owens wrote:
> > > If you actually have data on that, obviously that's different. But it
> > > sounds like you're guessing just like I am.
> >
> > I could only guess about other OS Vendors, one could check it also
> > for Ubuntu in their public git, but I don't think we need more data, as
> > ultimate judge here are Stable Maintainers
>
> Maybe I'm barking up the wrong tree, it's udev after all that decides to
> read the thing in /sys and name the interfaces differently because it's
> there...
Yeah, that's my feeling. Ideally there should be a systemd-networkd
setting that let's user opt out of adding the phys_port_name on
interfaces. 99% of users will not benefit from these, new drivers or
old. We're kinda making everyone suffer for the 1% :(
next prev parent reply other threads:[~2025-08-22 14:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 4:29 [Intel-wired-lan] [PATCH net] i40e: Prevent unwanted interface name changes Calvin Owens
2025-08-20 4:29 ` Calvin Owens
2025-08-20 6:42 ` [Intel-wired-lan] " Michal Schmidt
2025-08-20 6:42 ` Michal Schmidt
2025-08-20 9:41 ` [Intel-wired-lan] " Przemek Kitszel
2025-08-20 9:41 ` Przemek Kitszel
2025-08-20 16:11 ` [Intel-wired-lan] " Calvin Owens
2025-08-20 16:11 ` Calvin Owens
2025-08-20 23:09 ` [Intel-wired-lan] " Calvin Owens
2025-08-20 23:09 ` Calvin Owens
2025-08-20 15:31 ` [Intel-wired-lan] " Calvin Owens
2025-08-20 15:31 ` Calvin Owens
2025-08-20 17:41 ` [Intel-wired-lan] " Calvin Owens
2025-08-20 17:41 ` Calvin Owens
2025-08-21 8:00 ` [Intel-wired-lan] " Przemek Kitszel
2025-08-21 8:00 ` Przemek Kitszel
2025-08-21 14:23 ` [Intel-wired-lan] " Calvin Owens
2025-08-21 14:23 ` Calvin Owens
2025-08-21 20:39 ` [Intel-wired-lan] " Przemek Kitszel
2025-08-21 20:39 ` Przemek Kitszel
2025-08-22 4:23 ` [Intel-wired-lan] " Calvin Owens
2025-08-22 4:23 ` Calvin Owens
2025-08-22 6:30 ` [Intel-wired-lan] " Paul Menzel
2025-08-22 14:23 ` Jakub Kicinski [this message]
2025-08-22 14:23 ` Jakub Kicinski
2025-08-22 20:25 ` [Intel-wired-lan] " Jacob Keller
2025-08-24 18:59 ` Calvin Owens
2025-08-24 18:59 ` Calvin Owens
2025-08-20 15:51 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-08-20 15:51 ` Loktionov, Aleksandr
2025-08-20 23:16 ` Calvin Owens
2025-08-22 6:31 ` Paul Menzel
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=20250822072326.725475ef@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=calvin@wbinvd.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jedrzej.jagielski@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.