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] zfcp: Remove scsi_cmnd->serial_number from debug traces
Date: Wed, 29 Sep 2010 00:52:59 -0700	[thread overview]
Message-ID: <1285746779.18417.34.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20100928081103.GA3790@schmichrtp.mainz.de.ibm.com>

On Tue, 2010-09-28 at 10:11 +0200, Christof Schmitt wrote:
> From: Christof Schmitt <christof.schmitt@de.ibm.com>
> 
> With the change that drivers have to explicitly request the serial
> number for SCSI commands, this field should not be part of the zfcp
> traces. It is not worth the effort to request the serial number only
> for tracing purposes, so simply remove this field from the debug
> traces.
> 
> Reviewed-by: Swen Schillig <swen@vnet.ibm.com>
> Signed-off-by: Christof Schmitt <christof.schmitt@de.ibm.com>
> ---

Hi Christof,

This patch has been commited into the drop-host_lock-v5 branch and will
be included in the next RFC posting.

Thanks!

--nab

>  drivers/s390/scsi/zfcp_dbf.c |    4 ----
>  drivers/s390/scsi/zfcp_dbf.h |    2 --
>  2 files changed, 6 deletions(-)
> 
> --- a/drivers/s390/scsi/zfcp_dbf.c
> +++ b/drivers/s390/scsi/zfcp_dbf.c
> @@ -154,7 +154,6 @@ void _zfcp_dbf_hba_fsf_response(const ch
>  		scsi_cmnd = (struct scsi_cmnd *)fsf_req->data;
>  		if (scsi_cmnd) {
>  			response->u.fcp.cmnd = (unsigned long)scsi_cmnd;
> -			response->u.fcp.serial = scsi_cmnd->serial_number;
>  			response->u.fcp.data_dir =
>  				qtcb->bottom.io.data_direction;
>  		}
> @@ -330,7 +329,6 @@ static void zfcp_dbf_hba_view_response(c
>  			break;
>  		zfcp_dbf_out(p, "data_direction", "0x%04x", r->u.fcp.data_dir);
>  		zfcp_dbf_out(p, "scsi_cmnd", "0x%0Lx", r->u.fcp.cmnd);
> -		zfcp_dbf_out(p, "scsi_serial", "0x%016Lx", r->u.fcp.serial);
>  		*p += sprintf(*p, "\n");
>  		break;
>  
> @@ -881,7 +879,6 @@ void _zfcp_dbf_scsi(const char *tag, con
>  				}
>  				rec->scsi_result = scsi_cmnd->result;
>  				rec->scsi_cmnd = (unsigned long)scsi_cmnd;
> -				rec->scsi_serial = scsi_cmnd->serial_number;
>  				memcpy(rec->scsi_opcode, scsi_cmnd->cmnd,
>  					min((int)scsi_cmnd->cmd_len,
>  						ZFCP_DBF_SCSI_OPCODE));
> @@ -950,7 +947,6 @@ static int zfcp_dbf_scsi_view_format(deb
>  	zfcp_dbf_out(&p, "scsi_lun", "0x%08x", r->scsi_lun);
>  	zfcp_dbf_out(&p, "scsi_result", "0x%08x", r->scsi_result);
>  	zfcp_dbf_out(&p, "scsi_cmnd", "0x%0Lx", r->scsi_cmnd);
> -	zfcp_dbf_out(&p, "scsi_serial", "0x%016Lx", r->scsi_serial);
>  	zfcp_dbf_outd(&p, "scsi_opcode", r->scsi_opcode, ZFCP_DBF_SCSI_OPCODE,
>  		      0, ZFCP_DBF_SCSI_OPCODE);
>  	zfcp_dbf_out(&p, "scsi_retries", "0x%02x", r->scsi_retries);
> --- a/drivers/s390/scsi/zfcp_dbf.h
> +++ b/drivers/s390/scsi/zfcp_dbf.h
> @@ -110,7 +110,6 @@ struct zfcp_dbf_hba_record_response {
>  	union {
>  		struct {
>  			u64 cmnd;
> -			u64 serial;
>  			u32 data_dir;
>  		} fcp;
>  		struct {
> @@ -206,7 +205,6 @@ struct zfcp_dbf_scsi_record {
>  	u32 scsi_lun;
>  	u32 scsi_result;
>  	u64 scsi_cmnd;
> -	u64 scsi_serial;
>  #define ZFCP_DBF_SCSI_OPCODE	16
>  	u8 scsi_opcode[ZFCP_DBF_SCSI_OPCODE];
>  	u8 scsi_retries;


  reply	other threads:[~2010-09-29  7:57 UTC|newest]

Thread overview: 17+ 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 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
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 [this message]
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=1285746779.18417.34.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

all inboxes | Powered by JetHome®