Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Madhukar G <madhukar.linux@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Understanding SAS
Date: Fri, 31 Jul 2009 09:26:45 -0500	[thread overview]
Message-ID: <1249050405.3922.11.camel@mulgrave.site> (raw)
In-Reply-To: <e79524560907310456x7b2cf0c0h7e0453ceb55982fd@mail.gmail.com>

On Fri, 2009-07-31 at 17:26 +0530, Madhukar G wrote:
> I'm understanding SAS architecture for adaptec controller. I'm using
> the source adp94xx for the same. I was able to understand all the
> infomation unit flow but i'm stuck with one problem. I was not able to
> trace when task management IU shall be invoked.
> Do i need any special app to test task management IU?
> Is SCSI layer responsible for invoking task management IU?

I don't understand what you mean by IU:  SAS tends to think in terms of
frames (at the transport layer).  Information Units as used by the SAS
protocol means specific SSP frames.  Task Management in SAS has to
include SMP, STP and SATA as well.

However, SAM task management functions all map to the callbacks in
struct sas_domain_function_template which are called by libsas.  These
callbacks are also used for all other frame error handling.

James



  reply	other threads:[~2009-07-31 14:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31 11:56 Understanding SAS Madhukar G
2009-07-31 14:26 ` James Bottomley [this message]
2009-07-31 18:30   ` Madhukar G
     [not found]   ` <200908010930500463303@usish.com>
2009-08-01  5:38     ` Madhukar G
2009-08-04  6:28       ` Madhukar G
  -- strict thread matches above, loose matches on Subject: below --
2009-03-24 12:34 Madhukar G
     [not found] ` <FE3F06125A99254E8D92161AA4569C6F06A98B5F@sc-exch02.marvell.com>
2009-03-26  4:40   ` Madhukar G

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=1249050405.3922.11.camel@mulgrave.site \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=madhukar.linux@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox