From: Jiri Pirko <jiri@resnulli.us>
To: Dan Williams <dcbw@redhat.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Michal Kubecek <mkubecek@suse.cz>,
netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
David Ahern <dsahern@gmail.com>,
davem@davemloft.net, jakub.kicinski@netronome.com,
mlxsw@mellanox.com
Subject: Re: [RFC] longer netdev names proposal
Date: Fri, 28 Jun 2019 09:35:10 +0200 [thread overview]
Message-ID: <20190628073510.GB2236@nanopsycho> (raw)
In-Reply-To: <e3188fc08a13ddff9ea5a200a69aa6adbd9278ed.camel@redhat.com>
Thu, Jun 27, 2019 at 09:35:27PM CEST, dcbw@redhat.com wrote:
>On Thu, 2019-06-27 at 12:20 -0700, Stephen Hemminger wrote:
>> On Thu, 27 Jun 2019 20:39:48 +0200
>> Michal Kubecek <mkubecek@suse.cz> wrote:
>>
>> > > $ ip li set dev enp3s0 alias "Onboard Ethernet"
>> > > # ip link show "Onboard Ethernet"
>> > > Device "Onboard Ethernet" does not exist.
>> > >
>> > > So it does not really appear to be an alias, it is a label. To be
>> > > truly useful, it needs to be more than a label, it needs to be a
>> > > real
>> > > alias which you can use.
>> >
>> > That's exactly what I meant: to be really useful, one should be
>> > able to
>> > use the alias(es) for setting device options, for adding routes, in
>> > netfilter rules etc.
>> >
>> > Michal
>>
>> The kernel doesn't enforce uniqueness of alias.
>
>Can we even enforce unique aliases/labels? Given that the kernel hasn't
>enforced that in the past there's a good possibility of breaking stuff
>if it started. (unfortunately)
Correct. I think that Michal's idea to introduce "real aliases" is very
intereting. However, the existing "alias" as we have it does not seem
right to be used. Also because of the UAPI. We have IFLA_IFALIAS which
is a single value. For "real aliases" we need nested array.
[...]
next prev parent reply other threads:[~2019-06-28 7:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 9:43 [RFC] longer netdev names proposal Jiri Pirko
2019-06-27 15:29 ` Stephen Hemminger
2019-06-27 16:12 ` Dan Williams
2019-06-27 17:14 ` David Ahern
2019-06-27 18:08 ` Michal Kubecek
2019-06-27 18:23 ` Stephen Hemminger
2019-06-27 18:35 ` Andrew Lunn
2019-06-27 18:39 ` Michal Kubecek
2019-06-27 19:20 ` Stephen Hemminger
2019-06-27 19:35 ` Dan Williams
2019-06-28 7:35 ` Jiri Pirko [this message]
2019-06-28 11:12 ` Jiri Pirko
2019-06-28 11:42 ` Michal Kubecek
2019-06-28 12:25 ` Jiri Pirko
2019-06-28 13:14 ` Andrew Lunn
2019-06-28 13:55 ` Jiri Pirko
2019-06-28 15:44 ` Stephen Hemminger
2019-06-28 15:56 ` Jiri Pirko
2019-06-28 16:27 ` Michal Kubecek
2019-06-28 7:29 ` Jiri Pirko
2019-06-27 17:48 ` Jakub Kicinski
2019-06-27 17:56 ` Stephen Hemminger
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=20190628073510.GB2236@nanopsycho \
--to=jiri@resnulli.us \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=dsahern@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=mkubecek@suse.cz \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox