From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Ralph Sennhauser <ralph.sennhauser@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Gregory CLEMENT <gregory.clement@free-electrons.com>
Subject: Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces
Date: Wed, 24 Aug 2016 14:07:27 -0400 [thread overview]
Message-ID: <20160824180727.GE14311@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20160824191004.3b4ff2cb@gmail.com>
On Wed, Aug 24, 2016 at 07:10:04PM +0200, Ralph Sennhauser wrote:
> And in how many places this discrepancy was documented? You won't be
> able to update them all. Mailing lists, blogs, fora posts and what ever
> else. I'd say the damage is done and can't be fixed by simply changing
> the order now.
>
> Whether strong rule or not, obviously it went in so bending the rule is
> at least accepted. It's not what I have an issue with but with the
> reordering at this point.
>
> I'm clearly not convinced reverting would do more harm than good,
> otherwise I wouldn't have brought it up.
I would agree, although if you see below I think it maybe something
that user space will have to figure out a way to deal with sooner or
later anyhow.
> It's not about being able to fix the code or documentation but about
> having to do so in the first place.
>
> The nice thing about having the order in the dtb I thought was that it
> wont ever change.
I wonder, if someone was to build a box with this cpu, and add a PCIe
network device, which order would they get probed in? Any chance the
PCIe could grab eth0 before the mvneta devices get probed?
I also would not count on this not changing in the future potentially
by accident. The mmc block devices used to get probed in DTB order, then
that changed at some point and reordering the dtb no longer controlled it,
rather it was whichever device seemed to finish fastests, and then later
that was changed to using the controller's opinion of the device number
(which at least made it predicable again, even if not controllable from
the dtb).
So at the moment the dtb order controls ethernet probe order. Well if
other things have stopped doing that, why expect ethernet won't some
day stop doing that too?
"Fixing" the port numbering by reordering is hence a hack as far as I
am concerned and not certain to stay working long term.
> Going forward, as we disagree and it's basically a political decision,
> whom do we ask to rule here? Linus?
--
Len Sorensen
next prev parent reply other threads:[~2016-08-24 18:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 13:11 Ralph Sennhauser
2016-08-24 14:50 ` Thomas Petazzoni
2016-08-24 16:19 ` Lennart Sorensen
2016-08-24 16:43 ` Thomas Petazzoni
2016-08-24 17:10 ` Lennart Sorensen
2016-08-24 18:38 ` Lennart Sorensen
2016-08-24 17:10 ` Ralph Sennhauser
2016-08-24 18:07 ` Lennart Sorensen [this message]
2016-08-24 18:14 ` Thomas Petazzoni
2016-08-24 18:27 ` Lennart Sorensen
2016-08-24 19:52 ` Thomas Petazzoni
2016-08-24 20:51 ` Lennart Sorensen
2016-08-24 18:15 ` Thomas Petazzoni
2016-08-24 20:41 ` Ralph Sennhauser
2016-08-24 21:48 ` Jason Cooper
2016-08-25 7:38 ` Ralph Sennhauser
2016-08-25 19:40 ` Lennart Sorensen
2016-08-26 8:43 ` Gregory CLEMENT
2016-08-26 10:39 ` Ralph Sennhauser
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=20160824180727.GE14311@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=gregory.clement@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralph.sennhauser@gmail.com \
--cc=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®