From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: hannes@stressinduktion.org, max@rfc2324.org, netdev@vger.kernel.org
Subject: Re: [RFC] Stable interface index option
Date: Tue, 1 Dec 2015 12:20:38 -0800 [thread overview]
Message-ID: <20151201122038.795305df@xeon-e3> (raw)
In-Reply-To: <20151201.142847.1980856920707150414.davem@davemloft.net>
On Tue, 01 Dec 2015 14:28:47 -0500 (EST)
David Miller <davem@davemloft.net> wrote:
> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Tue, 1 Dec 2015 08:06:52 -0800
>
> > On Tue, 01 Dec 2015 17:02:23 +0100
> > Hannes Frederic Sowa <hannes@stressinduktion.org> wrote:
> >
> >> On Tue, Dec 1, 2015, at 16:50, Maximilian Wilhelm wrote:
> >> > > I'm not sure I understand how this would work- are we going to
> >> > > pin down the ifindex for some subset of interfaces?
> >> >
> >> > I'm not sure what your idea is, but I guess we might mean the same
> >> > thing:
> >> >
> >> > What I have in mind is that the user can supply a list of (ifname ->
> >> > ifindex) entries via a sysfs/procfs interface and if such a list is
> >> > present, the kernel will search the list for every ifname which is
> >> > registered and check if there is an entry. If there is, the ifindex
> >> > for this entry is used. If there is no entry found for the given
> >> > ifname, the usual algorithm is used (therefore inherently providing
> >> > backward compatibility).
> >>
> >> Sorry to ask because I don't like this feature at all. There was a lot
> >> of work on stable interface names. Why do you need stable ifindexes,
> >> which were never meant to be stable for a longer amount of time?
> >
> > Also current versions of SNMP provide more useful information about
> > network interface slot information in ifDescription
>
> Well if they do provide strings, then that is probably a better way
> forward than messing with the kernel.
It gives strings based on PCI information but nothing useful
on tunnels.
next prev parent reply other threads:[~2015-12-01 20:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 12:04 [RFC] Stable interface index option Maximilian Wilhelm
2015-12-01 15:34 ` Sowmini Varadhan
2015-12-01 15:50 ` Maximilian Wilhelm
2015-12-01 16:02 ` Hannes Frederic Sowa
2015-12-01 16:06 ` Stephen Hemminger
2015-12-01 19:28 ` David Miller
2015-12-01 20:20 ` Stephen Hemminger [this message]
2015-12-01 20:57 ` David Miller
2015-12-01 21:06 ` Sowmini Varadhan
2015-12-01 21:14 ` Hannes Frederic Sowa
2015-12-01 21:44 ` Stephen Hemminger
2015-12-01 21:54 ` Hannes Frederic Sowa
2015-12-01 22:31 ` Stephen Hemminger
2015-12-01 19:27 ` David Miller
2015-12-01 20:26 ` Hannes Frederic Sowa
2015-12-01 22:43 ` Maximilian Wilhelm
2015-12-01 23:58 ` Hannes Frederic Sowa
2015-12-02 1:41 ` Andrew Lunn
2015-12-02 11:03 ` Marcelo Ricardo Leitner
2015-12-01 16:11 ` Sowmini Varadhan
-- strict thread matches above, loose matches on Subject: below --
2015-12-01 16:10 Maximilian Wilhelm
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=20151201122038.795305df@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=max@rfc2324.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).