From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: mike.miller@hp.com, Jens.Axboe@oracle.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] HP (Compaq) Smart Array 5xxx controller SCSI driver
Date: Tue, 22 Jul 2008 09:40:31 -0500 [thread overview]
Message-ID: <1216737631.3364.17.camel@localhost.localdomain> (raw)
In-Reply-To: <20080719195150Y.fujita.tomonori@lab.ntt.co.jp>
On Sat, 2008-07-19 at 19:52 +0900, FUJITA Tomonori wrote:
> This is a SCSI driver for HP (Compaq) Smart Array 5xxx controllers.
>
> SCSI people can skip the following two paragraphs.
>
> Currently, a driver for HP (Compaq) Smart Array 5xxx controllers is
> implemented as a block device driver, block/cciss.c (aka, cciss). But
> the controller interface is SCSI-3 compatible. The specification says,
> "A controller that supports CISS is considered to be a SCSI storage
> array controller". A scsi driver for the controllers was discussed
> several times.
>
> I think that a SCSI cciss driver can be much simpler (and
> maintainable) than the block cciss driver (the majority of the code
> forging SCSI command can go away, we have the proper sysfs entries for
> free, we can handle scsi tape drives easily etc). It would be helpful
> for distributions too since they don't need stuff specific to cciss
> (such as udev rules).
>
>
> There isn't any easy migration path for users. So I think that we need
> to keep the block and scsi drivers for cciss for some time (say two
> years).
Actually, I think we can make one (which is really required ... it's a
lot of pain to move device nodes, just look at libata). It should be
child's play to come up with a udev rule that simply does extra symbolic
links from /dev/cciss<n>c<n>p<n> to whatever the sd device is. That
should hide a lot of the problem.
The other issue is plugging the management ioctl in, but that can be
done via scsi_host->ioctl.
James
next prev parent reply other threads:[~2008-07-22 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 10:52 [RFC PATCH] HP (Compaq) Smart Array 5xxx controller SCSI driver FUJITA Tomonori
2008-07-19 10:52 ` FUJITA Tomonori
2008-07-22 7:02 ` Hannes Reinecke
2008-07-22 7:02 ` Hannes Reinecke
2008-07-23 13:46 ` FUJITA Tomonori
2008-07-22 14:19 ` Miller, Mike (OS Dev)
2008-07-23 13:46 ` FUJITA Tomonori
2008-07-23 14:07 ` Miller, Mike (OS Dev)
2008-07-24 1:32 ` FUJITA Tomonori
2008-07-22 14:40 ` James Bottomley [this message]
2008-10-24 15:10 ` Miller, Mike (OS Dev)
2008-10-27 4:09 ` Douglas Gilbert
2008-10-27 4:54 ` FUJITA Tomonori
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=1216737631.3364.17.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Jens.Axboe@oracle.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mike.miller@hp.com \
/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.