mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Christof Schmitt <christof.schmitt@de.ibm.com>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
	Joe Eykholt <jeykholt@cisco.com>,
	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: Mon, 27 Sep 2010 16:02:28 -0700	[thread overview]
Message-ID: <1285628548.8880.64.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20100927140551.GB8473@schmichrtp.mainz.de.ibm.com>

On Mon, 2010-09-27 at 16:05 +0200, Christof Schmitt wrote:
> On Sat, Sep 18, 2010 at 12:57:58PM -0700, Nicholas A. Bellinger wrote:
> > On Fri, 2010-09-17 at 21:45 -0500, Mike Christie wrote:
> > > 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.
> > > 
> > 
> > In that case I will go ahead and add explict scsi_cmd_get_serial() calls
> > to the LLDs that use struct scsi_cmnd->serial_number in anything beyond
> > an obvious and simple informational purpose.
> > 
> > > You could also convert drivers to the host tagging if you needed a 
> > > unique id for each command sent to a host.
> > 
> > Hmmm, what does this entail again..?
> > 
> > > 
> > > > 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.
> > 
> > So I would suppose it would be OK for those drivers to continue to
> > printk serial_number to show the internal serial_number allocation is
> > now disabled by default.
> > 

<SNIP>

> > > 
> > > zfcp looks like it copies it. It does not look like the driver needs it.
> > > 
> > 
> > Ok, I will look at removing it's usage in zfcp or if necessary add an
> > the explict scsi_cmd_get_serial() call.
> 
> In zfcp, the serial_number is only accessed for writing it to debug
> traces. With the change that the driver has to request the serial
> number through use_serial_number, simply remove the serial number from
> zfcp.

Hi Christof,

So since the use of struct scsi_cmnd->serial_number is purely
informational for some LLDs (including zfcp) , I have been putting the
conversion of these LLDs as a low priority ATM.   I would happily accept
a patch to remove these.  8-)

Best,

--nab



  reply	other threads:[~2010-09-27 23:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
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-27 14:05       ` Christof Schmitt
2010-09-27 23:02         ` Nicholas A. Bellinger [this message]
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=1285628548.8880.64.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@suse.de \
    --cc=ak@linux.intel.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=christof.schmitt@de.ibm.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=michaelc@cs.wisc.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome