public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: Matthew Wilcox <willy@debian.org>
Cc: "'Christoph Hellwig'" <hch@infradead.org>,
	"Mukker, Atul" <Atulm@lsil.com>,
	"'Arjan van de Ven'" <arjanv@redhat.com>,
	"'James Bottomley'" <James.Bottomley@SteelEye.com>,
	"'Paul Wagland'" <paul@wagland.net>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: [SUBJECT CHANGE]: megaraid unified driver version 2.20.0.0-alpha1
Date: Wed, 25 Feb 2004 13:03:28 -0600	[thread overview]
Message-ID: <20040225130328.B14838@lists.us.dell.com> (raw)
In-Reply-To: <20040225173540.GB25779@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Wed, Feb 25, 2004 at 05:35:40PM +0000

On Wed, Feb 25, 2004 at 05:35:40PM +0000, Matthew Wilcox wrote:
> On Wed, Feb 25, 2004 at 11:28:39AM -0600, Matt Domsch wrote:
> > The list of PCI devices should be ordered in two buckets: ROMBs first,
> > then add in cards; secondarily, oldest to newest.  We do this with
> > aacraid today.
> 
> In 2.4, you can do what you like.  The list of PCI devices is in PCI
> bus number order, and that's the order you get when you use the hotplug
> interfaces.

Ahh, yes, of course.  

> Yes, this is a painful customer-visible change, but if they use scsi
> discs, they must already be used to devices changing name at random.

Well, to be fair, most people count on it not changing, i.e. it is
deterministic at least, such that if you don't change hardware or add
logical drives, you won't see any changes between boots.  For most
users, file system labels serve quite well to keep things consistent.
For swap, raw devices, and the like, devlabel or udev are used, but at
least devlabel (sorry Greg, I haven't played with udev too much yet)
uses SCSI inquiry page 83 or 80 data if it's there, which megaraid
doesn't provide.

For the install scenario, EDD (which megaraid *does* provide) will
suffice, but I need to get distro installers to start using it. ;-)
Oh, and get it working on x86-64.  That should be easy, soon as I have
access to such a system for a few days.


-- 
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

  reply	other threads:[~2004-02-25 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25  0:34 [SUBJECT CHANGE]: megaraid unified driver version 2.20.0.0-alpha1 Mukker, Atul
2004-02-25 12:58 ` Matthew Wilcox
2004-02-25 13:16 ` 'Christoph Hellwig'
2004-02-25 17:28   ` Matt Domsch
2004-02-25 17:35     ` Matthew Wilcox
2004-02-25 19:03       ` Matt Domsch [this message]
2004-02-25 14:28 ` Paul Wagland

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=20040225130328.B14838@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=Atulm@lsil.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=arjanv@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=paul@wagland.net \
    --cc=willy@debian.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