Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1765630AbXJPE5P (ORCPT ); Tue, 16 Oct 2007 00:57:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754548AbXJPE45 (ORCPT ); Tue, 16 Oct 2007 00:56:57 -0400 Received: from dsl081-033-126.lax1.dsl.speakeasy.net ([64.81.33.126]:45793 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755177AbXJPE4y (ORCPT ); Tue, 16 Oct 2007 00:56:54 -0400 Date: Mon, 15 Oct 2007 22:00:40 -0700 (PDT) From: david@lang.hm X-X-Sender: dlang@asgard.lang.hm To: Greg KH cc: Matthew Wilcox , Rob Landley , Julian Calaby , Theodore Tso , James Bottomley , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, Jens Axboe , Suparna Bhattacharya , Nick Piggin Subject: Re: What still uses the block layer? In-Reply-To: <20071016042104.GA7854@kroah.com> Message-ID: References: <200710112011.22000.rob@landley.net> <200710150304.00901.rob@landley.net> <646765f40710150206j75af4c4dwac4f4565451b64b1@mail.gmail.com> <200710150508.37332.rob@landley.net> <20071015173357.GB5738@kroah.com> <20071016040401.GA15744@parisc-linux.org> <20071016042104.GA7854@kroah.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1518 Lines: 35 On Mon, 15 Oct 2007, Greg KH wrote: > On Mon, Oct 15, 2007 at 10:04:01PM -0600, Matthew Wilcox wrote: >> On Mon, Oct 15, 2007 at 07:54:22PM -0700, david@lang.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). >> >> Greg probably has quite different examples. > > Changing the hardware (adding a new PCI device or removing one) are the > most common times this happens. But I have seen reports of this > happening when you upgrade/downgrade BIOS versions, and, in some > oops-we-messed-up cases, when we changed things in the kernel. BIOS upgrades qualify as changing hardware (or close to it) oops-we-messed-up cases of kernel changes don't justify 'best effort' nameing, it's a regression that needs to be fixed. now the other example given of docking a laptop is closer to reasonable (and is definantly a reason to have 'best effort' nameing as an option), but that's still a relativly special case, and it _is_ definantly changeing the hardware David Lang - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/