From: Mike Christie <mikenc@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>,
linux-iscsi-devel@lists.sourceforge.net,
Krishna Murthy <krmurthy@cisco.com>
Subject: Re: PATCH [3/5] qla2xxx: TCQ fixes
Date: Mon, 12 Jul 2004 17:19:58 -0700 [thread overview]
Message-ID: <40F32AAE.5070508@us.ibm.com> (raw)
In-Reply-To: <1089668486.1799.62.camel@mulgrave>
James Bottomley wrote:
> On Mon, 2004-07-12 at 09:05, Andrew Vasquez wrote:
>
>>ChangeSet
>> 1.1867 04/07/12 09:38:28 andrew.vasquez@apc.qlogic.com +2 -0
>> Correct usage of tag-command-queueing methods:
>
>
> I really don't think it is.
>
> For the way the qla2xxx works, the correct tag usage would be to use per
> HBA tags (which were introduced for aic7xxx but never used by them, so I
> haven't actually created the mid-layer API), to populate your queue
> handle field with the tag and to dispense with your outstanding_cmnds[]
> array and use scsi_find_tag() to get back the command from the handle.
>
> Since you'd be the first user of this API, I'd be happy to come up with
> it for a willing victim^Wvolunteer.
Depending on the API, we might be able to use it for the linux-iscsi
driver. Today the driver uses scsi_activate_tcq(), but does not uses the
tag numbers. Instead it uses its own initiator task tags values for
session wide identifiers, becuase we need tag values for iscsi ops. For
example if we need to send a ping how should we get a tag from the mid
layer? Or maybe becuase there are some transport specific tag values
should we use someting else or keep it in the driver?
Mike
next prev parent reply other threads:[~2004-07-13 0:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 14:05 PATCH [3/5] qla2xxx: TCQ fixes Andrew Vasquez
2004-07-12 21:41 ` James Bottomley
2004-07-13 0:19 ` Mike Christie [this message]
2004-07-13 2:28 ` Brian King
2004-07-13 14:29 ` James Bottomley
2004-07-13 14:27 ` James Bottomley
2004-07-13 19:04 ` [linux-iscsi-devel] " Mike Christie
2004-07-13 20:20 ` James Bottomley
2004-07-13 21:01 ` Mike Christie
-- strict thread matches above, loose matches on Subject: below --
2004-07-13 17:24 Andrew Vasquez
2004-07-13 17:43 ` James Bottomley
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=40F32AAE.5070508@us.ibm.com \
--to=mikenc@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=andrew.vasquez@qlogic.com \
--cc=krmurthy@cisco.com \
--cc=linux-iscsi-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox