From: Jeff Garzik <jgarzik@pobox.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: "Mukker, Atul" <Atulm@lsil.com>,
"'Matt Domsch'" <Matt_Domsch@dell.com>,
"'Christoph Hellwig'" <hch@infradead.org>,
"'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: Thu, 26 Feb 2004 02:49:04 -0500 [thread overview]
Message-ID: <403DA4F0.6060109@pobox.com> (raw)
In-Reply-To: <20040226074317.GC32246@devserv.devel.redhat.com>
Arjan van de Ven wrote:
> BTW it would be really nice if the various raid controller drivers could
> come up with a joint common IOCTL api since it seems every raid controller
> driver right now has a largely overlapping but yet different set of ioctls.
Well..... we should be moving away from ioctls for this.
For addressing raid arrays, inject REQ_SPECIAL requests directly into
the request_queue.
For addressing elements above raid array level (such as when creating
new arrays, etc.) there should be a character device that talks to the
host driver.
And please let's not bring that godawful SNIA API into the kernel ;-)
Jeff
next prev parent reply other threads:[~2004-02-26 7:49 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
2004-02-26 2:44 ` Matt Domsch
2004-02-26 7:43 ` Arjan van de Ven
2004-02-26 7:49 ` Jeff Garzik [this message]
-- 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=403DA4F0.6060109@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox