From: Mike Christie <michaelc@cs.wisc.edu>
To: Joe Eykholt <jeykholt@cisco.com>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Vasu Dev <vasu.dev@linux.intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Matthew Wilcox <willy@linux.intel.com>,
James Bottomley <James.Bottomley@suse.de>,
James Smart <james.smart@emulex.com>,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 01/11] scsi: Convert struct Scsi_Host->cmd_serial_number to atomic_t
Date: Fri, 17 Sep 2010 21:45:10 -0500 [thread overview]
Message-ID: <4C9427B6.9050404@cs.wisc.edu> (raw)
In-Reply-To: <4C93BB8E.2080501@cisco.com>
On 09/17/2010 02:03 PM, Joe Eykholt wrote:
>
> How about instead of adding use_serial_number, let's just have the
> drivers that want a serial number call scsi_cmd_get_serial()
I think this sounds better.
You could also convert drivers to the host tagging if you needed a
unique id for each command sent to a host.
> and stop calling it from scsi_dispatch_cmd()? AFAICT, it's only
> used in debug messages in some drivers. I didn't find other usages
> but didn't do an exhaustive search.
The comments for serial_number say that it is only supposed to be used
for debugging printks and most drivers use it for that. However, it
looks like mpt and dpt_i2o are using it for error handling and/or lookup
type of operations. I think the mpt* uses are not needed in the abort
checks.
And eata is using it for ordering and tracking or something. It could
probably be converted to the host tagging if or what you suggested if it
needs the uniqueue id.
zfcp looks like it copies it. It does not look like the driver needs it.
scsi_error.c uses it in scsi_try_to_abort_cmd to check if a command has
completed, but I think that can be done by checking if REQ_ATOM_COMPLETE
is set.
next prev parent reply other threads:[~2010-09-18 2:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 18:21 [PATCH v2 01/11] scsi: Convert struct Scsi_Host->cmd_serial_number to atomic_t Nicholas A. Bellinger
2010-09-17 18:21 ` Nicholas A. Bellinger
2010-09-17 19:03 ` Joe Eykholt
2010-09-17 19:33 ` Nicholas A. Bellinger
2010-09-18 2:45 ` Mike Christie [this message]
2010-09-18 2:56 ` Mike Christie
2010-09-18 19:57 ` Nicholas A. Bellinger
2010-09-23 21:46 ` Nicholas A. Bellinger
2010-09-24 6:32 ` Jens Axboe
2010-09-24 18:33 ` Mike Anderson
2010-09-24 20:57 ` Nicholas A. Bellinger
2010-09-25 2:31 ` Mike Christie
2010-09-24 20:41 ` Nicholas A. Bellinger
2010-09-24 20:41 ` Nicholas A. Bellinger
2010-09-27 14:05 ` Christof Schmitt
2010-09-27 23:02 ` Nicholas A. Bellinger
2010-09-28 8:11 ` [PATCH] zfcp: Remove scsi_cmnd->serial_number from debug traces Christof Schmitt
2010-09-29 7:52 ` Nicholas A. Bellinger
2010-09-28 3:14 ` [PATCH v2 01/11] scsi: Convert struct Scsi_Host->cmd_serial_number to atomic_t Matthew Wilcox
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=4C9427B6.9050404@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@suse.de \
--cc=ak@linux.intel.com \
--cc=andrew.vasquez@qlogic.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.smart@emulex.com \
--cc=jeykholt@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=tim.c.chen@linux.intel.com \
--cc=vasu.dev@linux.intel.com \
--cc=willy@linux.intel.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 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.