From: Mark Lord <lsml@rtr.ca>
To: dougg@torque.net
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] New QStor SATA/RAID Driver for 2.6.9-rc2
Date: Wed, 15 Sep 2004 08:47:44 -0400 [thread overview]
Message-ID: <414839F0.20008@rtr.ca> (raw)
In-Reply-To: <4147C38C.3000104@torque.net>
Douglas Gilbert wrote:
>>>
>>> Both hdparm and smartmontools are fully supported by this driver.
>
> I'm curious how smartmontools is supported. Does the driver
> support SCSI LOG SENSE commands on the physical units or does
> it take the 3ware/Marvell route?
> There is no sign of QStor specific code in smartmontools's CVS.
This driver simply implements the HDIO_DRIVE_CMD/HDIO_DRIVE_TASK
ioctl call (from Linux IDE). By doing so, it automatically gains
compatibility with smartmontools (-d ata), and with hdparm.
Currently, the implementation of those is native to the controller.
But eventually, I'd like to see it implement Curtis's ATA Passthrough
spec (to which I've been contributing).
Port selectors aside --> a nightmare for any sysadmin or driver writer
--> Linux has a huge unresolved issue for block devices.
It is currently next-to-impossible for a vendor to support a
new drive controller card under Linux unless it uses either SCSI
or libata. Doing one as a new block driver is not an option,
because of the installation issues for the end-user during the
first couple of years of deployment --> until the distros begin
to include the required /dev/ entries everywhere.
To solve this requires a nice generic /dev/ interface for disks,
common to all drivers which talk to such devices.
Currently on Linux, that interface is called "SCSI".
I think it might not be unreasonable to gradually evolve
the SCSI host interface to include, say, a non-translating
queuecommand() method, and associated pals.
This would get rid of much (not all) of the double-translation objection,
and provide a smooth path for supporting Firewire, USB, parallel-port,
SATA, ATA, and of course SCSI, disks all under one naming subsystem.
We practically have that already today.
The SCSI mid-layer is a nice generic block device glue system.
We just need perhaps to make it less SCSI-specific.
Cheers
--
Mark Lord
(hdparm keeper & the original "Linux IDE Guy")
next prev parent reply other threads:[~2004-09-15 12:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 15:43 [PATCH] New QStor SATA/RAID Driver for 2.6.9-rc2 Mark Lord
2004-09-14 16:21 ` Jeff Garzik
2004-09-14 16:23 ` Jeff Garzik
2004-09-14 16:39 ` Nathan Bryant
2004-09-14 17:02 ` Jeff Garzik
2004-09-15 4:22 ` Douglas Gilbert
2004-09-15 4:30 ` Jeff Garzik
2004-09-15 12:47 ` Mark Lord [this message]
2004-09-15 12:55 ` Jens Axboe
2004-09-15 13:13 ` Matthew Wilcox
2004-09-15 16:14 ` Jeff Garzik
2004-09-15 7:02 ` Christoph Hellwig
[not found] <41471163.10709@rtr.ca>
2004-09-14 17:00 ` Jeff Garzik
2004-09-14 17:27 ` Mark Lord
2004-09-14 17:33 ` Jeff Garzik
2004-09-14 17:51 ` Mark Lord
2004-09-14 17:56 ` Jeff Garzik
2004-09-14 18:03 ` Mark Lord
2004-09-14 18:07 ` Jeff Garzik
2004-09-14 18:08 ` Jeff Garzik
2004-09-14 18:25 ` James Bottomley
2004-09-14 18:35 ` Jeff Garzik
2004-09-14 18:51 ` James Bottomley
2004-09-15 2:39 ` Mark Lord
2004-09-15 2:47 ` Jeff Garzik
2004-09-15 12:35 ` Mark Lord
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=414839F0.20008@rtr.ca \
--to=lsml@rtr.ca \
--cc=dougg@torque.net \
--cc=jgarzik@pobox.com \
--cc=linux-scsi@vger.kernel.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