From: Matt Domsch <Matt_Domsch@dell.com>
To: "'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>,
Matthew Wilcox <willy@debian.org>,
"'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 11:28:39 -0600 [thread overview]
Message-ID: <20040225112839.A14838@lists.us.dell.com> (raw)
In-Reply-To: <20040225131640.A3966@infradead.org>; from hch@infradead.org on Wed, Feb 25, 2004 at 01:16:40PM +0000
On Wed, Feb 25, 2004 at 01:16:40PM +0000, 'Christoph Hellwig' wrote:
> On Tue, Feb 24, 2004 at 07:34:01PM -0500, Mukker, Atul wrote:
> > 2. Controller and device re-ordering on both lk 2.4 and lk 2.6. If this
> > is not desired, the driver code would be modified to make it PCI ordered
> > detection. The driver also re-orders the drives, based on which one is
> > chosen as boot drive. Matt, please add your comments here.
>
> This is a bad thing for 2.6, don't do it. For 2.4 just leave the probe code as
> it is there currently - any change during the stable series just confuses
> users.
I agree with Christoph here. megaraid is the only driver that I've
worked with that does this device reordering thing; none of the other
SCSI drivers we use regularly does, and it's not a feature that I've
advertised to customers when they come asking. It would help greatly
if the firmware could export unique numbers akin to SCSI inquiry page
83 for each logical drive on each controller, such that we could
actually use udev and friends well. I've asked for this feature for
several years, and I know it's not yet on the firmware roadmaps.
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.
Thanks,
Matt
--
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
next prev parent reply other threads:[~2004-02-25 17:29 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 [this message]
2004-02-25 17:35 ` Matthew Wilcox
2004-02-25 19:03 ` Matt Domsch
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=20040225112839.A14838@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