public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Jan Wagner <jwagner@kurp.hut.fi>, linux-kernel@vger.kernel.org
Subject: Re: support for sata7 Streaming Feature Set?
Date: Thu, 18 May 2006 09:18:45 -0400	[thread overview]
Message-ID: <446C7435.2040809@rtr.ca> (raw)
In-Reply-To: <446BD8F2.10509@gmail.com>

Tejun Heo wrote:
> Jan Wagner wrote:
>> Hi and thanks for your response,
>>
>> On Sun, 14 May 2006, Tejun Heo wrote:
>>>> anyone know if the now already somewhat old Streaming Feature Set of
>>>> ATA/ATAPI 7 is going to be implemented in the kernel ata functions?
>>>>
>>>> According to one web site that contains hdreg.h
>>>> http://www.koders.com/c/fidCD7293464D782E48F93EEF8A71192F1BF28FC205.aspx 
...
That link just gives me a search page.  Got a better link?


> No, it's not a horrible hack.  Again, no one thinks smartd is a horrible 
> hack.  Even core things like irqbalancing and CPU speeding down are 
> controlled from userland.  Being in the userland is a good thing - it's 
> much safer & more convenient/flexible out there.
> 
>>> What are you gonna use it for?
>>
>> To record or play back real-time continuous streamed data that is not
>> error-critical but delay critical, from/to a bidirectional data
>> aquisition card at ~1Gbit/s over longer time spans.
..
Other uses include tons of embedded systems using Linux,
primarily those that handle any kind of A/V record/playback
(think "Tivo", MP3 player, video players, ...).
These are about as rare as a fileserver, when counting the installed base.

I think that the ATA streaming feature set cannot be done
efficiently (which is the whole point of it!) without some kernel support.

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.

But how to handle it all nicely is the real question.
A new block driver, if libata cannot handle it?

Cheers

  reply	other threads:[~2006-05-18 13: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 [this message]
2006-05-18 15:38         ` Jeff Garzik
2006-05-18 23:18           ` Tejun Heo
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=446C7435.2040809@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=htejun@gmail.com \
    --cc=jwagner@kurp.hut.fi \
    --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