public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Michael Heinz <mheinz@infiniconsys.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Task Sets in SCSI and Linux
Date: Wed, 08 May 2002 11:34:40 -0500	[thread overview]
Message-ID: <200205081634.g48GYe304381@localhost.localdomain> (raw)
In-Reply-To: Message from Michael Heinz <mheinz@infiniconsys.com> of "Wed, 08 May 2002 10:54:48 EDT." <8B024BD9-6293-11D6-B607-0003934B22FE@infiniconsys.com>

mheinz@infiniconsys.com said:
>  From perusing the source code it appears to me that the Linux SCSI
> layers do not take advantage of SCSI task sets. Is that correct? 

Could you elaborate on what you mean by "task set"?  SCSI 3 defines a task 
simply as "work to be performed by the logical unit in the form of a command 
or a group of linked commands".  This basically means the I_T_L or I_T_L_Q 
nexus of scsi2, however scsi3 expands this for multi-ported devices.  "task 
set" usually just means the outstanding tasks on a given logical unit, and as 
such it's really a target concept although the initiator must know how to 
track outstanding tasks correctly.

If by "take advantage of SCSI task sets" you mean use tagged tasks to get 
multiple outstanding tasks on a logical unit, the answer is yes but it depends 
on the low level driver implementation.

James Bottomley



  reply	other threads:[~2002-05-08 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 14:28 aix7xxx driver 5.2.4/5.2.0 vs. 6.2.5 with onboard aic7896/97 Ultra2 controller Dimitrios P. Bouras
2002-05-07 14:31 ` Justin T. Gibbs
2002-05-07 14:45   ` Doug Ledford
2002-05-08 13:20   ` Dimitrios P. Bouras
2002-05-08 14:54     ` Task Sets in SCSI and Linux Michael Heinz
2002-05-08 16:34       ` James Bottomley [this message]
2002-05-08 16:51         ` Matthew Jacob
2002-05-08 16:56           ` Matthew Jacob
2002-05-08 17:22         ` Michael Heinz
2002-05-08 18:29           ` Kurt Garloff

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=200205081634.g48GYe304381@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mheinz@infiniconsys.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