From: Jeff Garzik <jgarzik@pobox.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Luben Tuikov <luben_tuikov@adaptec.com>,
dougg@torque.net, linux-scsi@vger.kernel.org,
Tejun Heo <htejun@gmail.com>
Subject: Re: [PATCH] libata: write cache and read ahead
Date: Wed, 24 Aug 2005 06:06:29 -0400 [thread overview]
Message-ID: <430C46A5.1050702@pobox.com> (raw)
In-Reply-To: <20050824091641.GD26447@infradead.org>
Christoph Hellwig wrote:
> On Tue, Aug 23, 2005 at 07:22:59PM -0400, Luben Tuikov wrote:
>
>>On 08/22/05 01:12, Douglas Gilbert wrote:
>>
>>>I was surprised how much code needed changing.
>>>With MODE SELECT's issues with libata addressed
>>>various other SAT "extras" should be much easier
>>>to implement. That should make libata more attractive
>>>as a SAT layer for SAS LLDDs (that don't do it already
>>>in firmware).
>>
>>Doug, how about never needing a SAT layer for SAS LLDDs
>>for ATA/ATAPI devices.
>>
>>Would you object if I "give" you a "domain device" to which
>>you can send FISes (+ the packet if ATAPI) through
>>a SAM-4 intefrace: Execute Task + TMFs?
>
>
> Personally I think that would be nice, but when I mentioned the basic idea
> (sending FISes through BLOCK_PC block later commands and let the scsi layer
> handle then as vendor-specific commands) Jeff didn't like that because
> then we'd need a non-sd upper driver although using the scsi midlayer.
That's something different than when Luben was talking about.
Addressing what you [Christoph] are talking about, the block layer needs
to grow a generic method for submitting device commands, be they ATA,
SCSI, SCSI w/ variable-length CDB, I2O, Promise SX8 message, whatever.
Stuff that into the request_queue, and the transport driver handles it
from there.
Jeff
next prev parent reply other threads:[~2005-08-24 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 10:06 [PATCH] libata: write cache and read ahead Douglas Gilbert
2005-08-21 23:56 ` Jeff Garzik
2005-08-22 5:12 ` Douglas Gilbert
2005-08-22 5:34 ` Jeff Garzik
2005-08-23 23:22 ` Luben Tuikov
2005-08-24 9:16 ` Christoph Hellwig
2005-08-24 10:06 ` Jeff Garzik [this message]
2005-08-24 10:04 ` Jeff Garzik
2005-08-24 16:28 ` Luben Tuikov
2005-08-24 11:03 ` Douglas Gilbert
2005-08-24 16:41 ` Luben Tuikov
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=430C46A5.1050702@pobox.com \
--to=jgarzik@pobox.com \
--cc=dougg@torque.net \
--cc=hch@infradead.org \
--cc=htejun@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
/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.