public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: "Heinz, Michael" <mheinz@infiniconsys.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Revisiting task tags and Linux SCSI
Date: Thu, 09 May 2002 09:10:22 -0400	[thread overview]
Message-ID: <200205091310.g49DAMB01883@localhost.localdomain> (raw)
In-Reply-To: Message from "Heinz, Michael" <mheinz@infiniconsys.com> of "Wed, 08 May 2002 23:01:11 EDT." <08628CA53C6CBA4ABAFB9E808A5214CB0C5E9D@mercury.infiniconsys.com>

mheinz@infiniconsys.com said:
> Maybe I'm an idiot - but I cannot find *anywhere* in sd.c, sg.c,
> scsi.c or elsewhere that the scsi_cmnd.tag field is set to anything
> except zero, nor can I find anywhere in the high level SCSI drivers
> that the "scsi_device.tagged_*" fields are used. 

> Am I wrong here? I can certainly generate task tags that are
> guaranteed to be unique (I already have to do that anyway), and I can
> certainly 'or' them with ORDERED_QUEUE_TAG but I'm not sure how that's
> going to impact the higher level SCSI drivers since they never pay
> attention to the values of any of the "tagged_*" fields anyway..... 

No, you're not wrong.  In the current layering model, tags are manipulated 
almost exclusively by the low level drivers (see aic7xxx, sym8xxx, 53c700 for 
details).  If you use a LLD without TCQ support, then you only send one 
command per lun.

scsi_cmnd.tag is really never used, I believe.

This is counter intuitive since tag manipulation functions should be higher up 
in the driver stack, but that's the way it works today.  Jens Axboe is working 
on generic tag functions (look in block/ll_rw_block.c) but they were only 
introduced recently and aren't yet used in the SCSI layer at all.

James Bottomley



  parent reply	other threads:[~2002-05-09 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09  3:01 Revisiting task tags and Linux SCSI Heinz, Michael
2002-05-09  3:35 ` Matthew Jacob
2002-05-09 13:10 ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-10 12:38 Heinz, Michael

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=200205091310.g49DAMB01883@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