[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0710152110370.1538@asgard.lang.hm>
Date: Mon, 15 Oct 2007 21:15:43 -0700 (PDT)
From: david@...g.hm
To: Matthew Wilcox <matthew@....cx>
cc: Greg KH <greg@...ah.com>, Rob Landley <rob@...dley.net>,
Julian Calaby <julian.calaby@...il.com>,
Theodore Tso <tytso@....edu>,
James Bottomley <James.Bottomley@...eleye.com>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
Jens Axboe <axboe@...e.de>,
Suparna Bhattacharya <suparna@...ibm.com>,
Nick Piggin <piggin@...erone.com.au>
Subject: Re: What still uses the block layer?
On Mon, 15 Oct 2007, Matthew Wilcox wrote:
> On Mon, Oct 15, 2007 at 07:54:22PM -0700, david@...g.hm wrote:
>> do PCI devices reorder their bus numbers spontaniously, or only if you
>> change the hardware?
>
> The only system I've had that reordered PCI bus numbers was when I had a
> partitionable system and changed the partitioning. Not quite "change
> the hardware", but neither was it "spontaneous". It was certainly
> unexpected (for me).
Ok, I would class that as the equivalent of 'changing the hardware'.
> Greg probably has quite different examples.
I would definantly be interested in hearing some of them. Greg's comment
makes it sound like this is something that (with modern hardware) could
happen to anyone at any time (which, if true, would be sufficiant to
require 'best effort' nameing of devices for everything), while my
experiance is that if the hardware is static (i.e. you don't plugin or
unplug PCI devices) the numbering of exisitng PCI devices and buses is
static. and while I understand that consumer distros want to have
everything 'best effort' named to make it easier for users, I disagree
that this should force everyone to use 'best effort' when there are many
situations where it's unnessasary overhead and chances for errors.
David Lang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists