Proposed F19 Feature: systemd/udev Predictable Network Interface Names

[John Reiser]

On 02/28/2013 06:55 AM, Kay Sievers wrote:
> On Mon, Feb 25, 2013 at 6:02 PM, Andy Gospodarek <agospoda at redhat.com> wrote:
> 
>>>> I'd like to see kernel driver work to be sure every multi-port driver
>>>> with the same PCI b/d/b/f sets dev_id.  That isn't necessarily true
>>>> today, which makes it hard to trust.  biosdevname needs this too,
>>>> until such a time as it's dead.
> 
>>> Do we have a list of these, or is it a matter of doing a driver audit?
>>> CC'ing gospo.
> 
>> Right now almost no drivers actually set dev_id.  In fact mlx4_en,
>> cxgb4, and sfc seem to be the only ones right now.  If we feel like this
>> a requirement there will be work on the kernel side to add this.
> 
> This only matters if there are multiple devices created by a driver
> for one and the same pci device. Like when we have only one entry in
> lspci, but multiple interfaces of the same type having this one device
> as a parent.
> 
> Is this really common? I would expect this is a very rare exception.

How does this relate to a hosting service which assigns a different IP4
for each client domain to the same physical ethernet port?  My service
has many dozen different IP4 [advertised via DNS] assigned to the same port.

--