From: Luben Tuikov <tluben@rogers.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: "do ata" scsi command?
Date: Fri, 16 May 2003 14:50:47 -0400 [thread overview]
Message-ID: <3EC53307.5070908@rogers.com> (raw)
In-Reply-To: <20030515230223.GA516@gtf.org>
Jeff Garzik wrote:
> In terms of a userspace interface for my ata-over-scsi gadget, I would
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The main point.
> prefer to use /dev/sg instead of inventing a totally new interface.
> That, in turn, implies a need for a "do ata taskfile" scsi command,
> which is sorta like ATAPI in reverse: we are wrapping a raw ata
> taskfile inside a scsi cdb.
>
> My question is, does an existing standard or spec exist for such an idea?
>
> If not, I'll just roll my own.
I read the whole thread.
It seems like you want what the 3ware LLDD is doing. The format
and specs are closed, but the implementation is open: ioctl
and a char device ioctl.
What you lose is the block/scsi synchronizaion, but if you want
to support _closed_ vendor extensions, that's what you get.
Unless what you want to support has a command mapping already
in SCSI? Did you check SBC-2, SMC-2, SCC-2, SES-2? Wouldn't
you find any CDB's there which would fit in? My guess is not.
Did you also check the mode pages, etc?
--
Luben
next prev parent reply other threads:[~2003-05-16 18:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 23:02 "do ata" scsi command? Jeff Garzik
2003-05-16 6:03 ` Jens Axboe
2003-05-16 15:54 ` Jeff Garzik
2003-05-16 16:05 ` Jens Axboe
2003-05-16 16:30 ` Jeff Garzik
2003-05-16 16:35 ` Jens Axboe
2003-05-16 16:41 ` Jeff Garzik
2003-05-16 16:43 ` Jens Axboe
2003-05-16 16:46 ` Jeff Garzik
2003-05-17 4:17 ` Douglas Gilbert
2003-05-17 7:49 ` Luben Tuikov
2003-05-16 16:35 ` Jeff Garzik
2003-05-16 16:40 ` Jens Axboe
2003-05-16 16:45 ` Jeff Garzik
2003-05-16 18:37 ` Andries Brouwer
2003-05-16 19:02 ` Luben Tuikov
2003-05-16 18:50 ` Luben Tuikov [this message]
2003-05-16 19:31 ` 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=3EC53307.5070908@rogers.com \
--to=tluben@rogers.com \
--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 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.