From: Jeff Garzik <jgarzik@pobox.com>
To: "Mukker, Atul" <Atulm@lsil.com>
Cc: 'Matt Domsch' <Matt_Domsch@dell.com>,
'Christoph Hellwig' <hch@infradead.org>,
'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-al pha1
Date: Wed, 25 Feb 2004 21:38:36 -0500 [thread overview]
Message-ID: <403D5C2C.7000205@pobox.com> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57033BC3EA@exa-atlanta.se.lsil.com>
Mukker, Atul wrote:
> With multiple adapters, applications would need to open multiple handles.
> This would somewhat complicate things for them. But keeping in line with
> general expectations, we would fork the drivers for different class of
> controllers now.
"opening multiple handles" is preferred. You want one discrete object
per controller or per device, depending on the object in question.
> I have not yet gotten strong feelings against a single driver for lk 2.4 and
> lk 2.6. If this is true, we would like to keep single driver for both
> kernels - since lk 2.4 still has a big lifecycle.
If you are doing multiple drivers in 2.6, it would seem better to match
that as closely as possible in 2.4.
> For lk 2.6, the controllers would be detected PCI ordered and because of
> existing lk 2.4 setups, driver would re-order the registration based on boot
> controller.
Look at my libata code -- in both 2.4 and 2.6, it uses the proper PCI
API calls.
Controller order is irrelevant -- device order is what you really care
about, right? This can be managed by creating a list during probe, and
then executing the list after all controllers have been probed.
Obviously, this excludes hotplug controllers added after the initial
module_init() function exits.
Jeff
next prev parent reply other threads:[~2004-02-26 2:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 23:05 [SUBJECT CHANGE]: megaraid unified driver version 2.20.0.0-al pha1 Mukker, Atul
2004-02-26 2:38 ` Jeff Garzik [this message]
2004-02-26 2:44 ` Matt Domsch
2004-02-26 7:43 ` Arjan van de Ven
2004-02-26 7:49 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-03-19 22:17 Mukker, Atul
2004-03-19 22:26 ` Matthew Wilcox
2004-02-26 15:21 Mukker, Atul
2004-02-25 20:41 Mukker, Atul
2004-02-25 20:38 Mukker, Atul
2004-02-25 20:44 ` 'Christoph Hellwig'
2004-02-25 21:38 ` Matt Domsch
2004-02-26 2:27 ` Jeff Garzik
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=403D5C2C.7000205@pobox.com \
--to=jgarzik@pobox.com \
--cc=Atulm@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=Matt_Domsch@dell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.