From: Mark Lord <lkml@rtr.ca>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Jeff Garzik <jgarzik@pobox.com>,
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 13:44:33 -0400 [thread overview]
Message-ID: <4124E701.5020905@rtr.ca> (raw)
In-Reply-To: <200408191751.19101.bzolnier@elka.pw.edu.pl>
The READ/WRITE SECTOR commands are not actually used by
any software I know of with HDIO_DRIVE_CMD, so no big deal there.
The ioctl should be limited to SET_FEATURES, IDENTIFY, and SMART.
And you'll get no debate from me on wanting a better interface
moving forward -- I really like the new ATA Command Pass-Through
draft spec (updated today, by the way).
But there'll need to be some overlap between the old and new,
and currently the libata driver has no way for smartmontools
or hdparm to communicate and control drive features like
the cache/readahead settings, and the various SMART capabilities.
Simply dropping HDIO_DRIVE_CMD/HDIO_DRIVE_TASK into there would
immediately gain full compatibility with the existing toolsets,
and give some time for a newer scheme to be rolled out in the
kernel, the tools, and ultimately all of the various distros.
Cheers
--
Mark Lord
(hdparm keeper & the original "Linux IDE Guy")
next prev parent reply other threads:[~2004-08-19 17:45 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 [this message]
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
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=4124E701.5020905@rtr.ca \
--to=lkml@rtr.ca \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).