From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Mark Lord <lkml@rtr.ca>, Jan Wagner <jwagner@kurp.hut.fi>,
linux-kernel@vger.kernel.org
Subject: Re: support for sata7 Streaming Feature Set?
Date: Fri, 19 May 2006 08:18:45 +0900 [thread overview]
Message-ID: <446D00D5.2040006@gmail.com> (raw)
In-Reply-To: <446C9503.1020609@garzik.org>
Jeff Garzik wrote:
> Mark Lord wrote:
>> The device driver has to know about it, at a minimum so that it can
>> select a different EH protocol for the streams. Which in turn means
>> that the streaming commands should be known to the driver as well.
>
> Different taskfile protocol, you mean?
I haven't checked all the docs and codes thoroughly but I don't see a
need for new protocol or anything. When a streaming command fails due
to failing to meet timing constraints, it fails w/ device error. sg can
adjust retry count and the device error will be reported without much
recovery action (only revalidation). If the device fails due to some
other reasons (say HSM violation), it needs full EH no matter what.
Without full EH, it becomes completely unusable.
>> But how to handle it all nicely is the real question.
>> A new block driver, if libata cannot handle it?
>
> I seriously doubt writing a whole new ATA driver subsystem will fly :)
All I can see are little extensions to sg interface and maybe libata. I
don't think it needs full-blown in-kernel driver. However, to use this
feature with a filesystem, we would need to build a block map of the
file to use. I think such feature is already provided and used by
LILO/GRUB kinds of things.
--
tejun
next prev parent reply other threads:[~2006-05-18 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 12:54 support for sata7 Streaming Feature Set? Jan Wagner
2006-05-14 7:06 ` Tejun Heo
2006-05-17 8:30 ` Jan Wagner
2006-05-17 13:40 ` Lennart Sorensen
2006-05-18 9:33 ` Jan Wagner
2006-05-18 2:16 ` Tejun Heo
2006-05-18 13:18 ` Mark Lord
2006-05-18 15:38 ` Jeff Garzik
2006-05-18 23:18 ` Tejun Heo [this message]
2006-05-19 15:16 ` Mark Lord
2006-05-18 15:36 ` Jeff Garzik
2006-05-18 23:12 ` Tejun Heo
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=446D00D5.2040006@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=jwagner@kurp.hut.fi \
--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