All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Luben Tuikov <luben_tuikov@adaptec.com>
Cc: 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:04:00 -0400	[thread overview]
Message-ID: <430C4610.3080205@pobox.com> (raw)
In-Reply-To: <430BAFD3.9000702@adaptec.com>

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?
> 
> Jeff?

SAT is the useful piece of libata that makes everything work.  You can't 
rip out it and still expect to do anything useful ;-)

libata relies on SCSI's device class drivers -- sd, sr, st, sg -- to 
manage devices and generate commands to service.  And in turn, we rely 
on SAT (libata-scsi.c) to translate device class commands into ATA commands.

If the SAT layer went away, then nothing would exist to generate 
commands for libata to service.

	Jeff




  parent reply	other threads:[~2005-08-24 10:04 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
2005-08-24 10:04       ` Jeff Garzik [this message]
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=430C4610.3080205@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=dougg@torque.net \
    --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.