All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Paul Brook <paul@codesourcery.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org,
	Bique Alexandre <alexandre.bique@citrix.com>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] ATAPI pass through
Date: Wed, 1 Jul 2009 13:29:31 +0200	[thread overview]
Message-ID: <20090701112931.GC10455@lst.de> (raw)
In-Reply-To: <200907011036.02874.paul@codesourcery.com>

On Wed, Jul 01, 2009 at 10:36:01AM +0100, Paul Brook wrote:
> IIRC ATAPI and SCSI are not the same. They provide very similar functionality, 
> however the actual commands are different.

ATAPI has somewhat more limited command sets, mostly because it does not
support the traditional 6 byte commands and doesn't support the scsi
block commands (SBC) used for disks.  For CDROMs both traditional
parallel scsi and atap use the same command set (MMC in various
revisions)

> While it is possible to connect SATA drives to a SAS HBA, I believe this is 
> done by tunneling IDE/ATAPI commands, rather then using native SCSI commands.

There are no ATAPI hard drives, just plain ATA which is not a SCSI
command set at all.  For directly connected disks on a SAS HBA the HBA
speaks plain SATA to the disk (as the SAS and SATA link layers are the
same).  If you connect a SATA disk to a SAS expander the expander talks
SATA to the disk and the expander encapsulates it in STP which is just a
thin layer of SAS routing information around the ATA command block,
similar to the SSP protocol used to talk to SCSI devices which is a thin
layer around SCSI command blocks.

I would expect an ATAPI cdrom attached to a SAS expander to talk MMC
command blocks over ATAPI over STP, but I haven't actually seen this
setup in practice.

  reply	other threads:[~2009-07-01 11:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 15:34 [Qemu-devel] [PATCH] ATAPI pass through Bique Alexandre
2009-06-30 16:26 ` Kevin Wolf
2009-06-30 18:10   ` Bique Alexandre
2009-07-01  6:57   ` Alexander Graf
2009-07-01  8:44     ` Christoph Hellwig
2009-07-01  9:36     ` Paul Brook
2009-07-01 11:29       ` Christoph Hellwig [this message]
2009-06-30 17:01 ` Christoph Hellwig
2009-06-30 17:55   ` Bique Alexandre
2009-07-01  8:43     ` Christoph Hellwig

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=20090701112931.GC10455@lst.de \
    --to=hch@lst.de \
    --cc=agraf@suse.de \
    --cc=alexandre.bique@citrix.com \
    --cc=kwolf@redhat.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.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 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.