From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: new tool: blktool
Date: Thu, 19 Aug 2004 14:12:23 -0400 [thread overview]
Message-ID: <4124ED87.6040702@pobox.com> (raw)
In-Reply-To: <4124EB91.60706@rtr.ca>
Mark Lord wrote:
> >* I don't mind HDIO_DRIVE_TASK nearly as much as HDIO_DRIVE_CMD,
> >* since the command protocol is available.
>
> That's not HDIO_DRIVE_TASKFILE, by the way.. a different beast there.
>
> HDIO_DRIVE_TASK is just a slightly different form of HDIO_DRIVE_CMD
> for non-data commands (specifically, some SMART commands),
> with a more complete register set being exchanged.
Oops, indeed I meant HDIO_DRIVE_TASKFILE.
Anyway, once the infrastructure for the ATA Pass-thru CDB is implemented
in libata, it is trivial to implement any of these three HDIO_DRIVE_xxx
ioctls, using the ioctl data to build a scsi command internally. A bit
strange at first glance, but it maximizes the leverage of existing
kernel infrastructure to send commands, time them out, etc.
Jeff
next prev parent reply other threads:[~2004-08-19 18:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 21:36 new tool: blktool Jeff Garzik
2004-08-15 20:55 ` Alan Cox
2004-08-15 22:07 ` Jeff Garzik
2004-08-15 22:18 ` David Ford
2004-08-15 22:22 ` Anton Starikov
2004-08-15 22:40 ` Jeff Garzik
2004-08-15 23:00 ` Anton Starikov
2004-08-15 23:27 ` Mark Lord
2004-08-15 23:34 ` Mark Lord
2004-08-15 23:44 ` Jeff Garzik
2004-08-15 23:36 ` Jeff Garzik
2004-08-16 2:36 ` Mark Lord
2004-08-16 16:53 ` Jeff Garzik
2004-08-19 15:03 ` Mark Lord
2004-08-19 15:51 ` Bartlomiej Zolnierkiewicz
2004-08-19 17:44 ` Mark Lord
2004-08-19 17:50 ` Jeff Garzik
2004-08-19 17:57 ` Jeff Garzik
2004-08-19 18:01 ` Mark Lord
2004-08-19 18:04 ` Mark Lord
2004-08-19 18:12 ` Jeff Garzik [this message]
2004-08-19 18:42 ` 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=4124ED87.6040702@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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;
as well as URLs for NNTP newsgroup(s).