All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Andre Hedrick <andre@pyxtechnologies.com>
Cc: Douglas Gilbert <dougg@torque.net>,
	"J. E. J. Bottomley" <James.Bottomley@SteelEye.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.18-modified-scsi-h.patch
Date: Tue, 19 Nov 2002 01:28:51 -0500	[thread overview]
Message-ID: <3DD9DA23.1070102@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10211182138310.2779-200000@master.linux-ide.org>

Andre Hedrick wrote:

> Greetings Doug et al.
>
> Please consider the addition of this simple void ptr to the scsi_request
> struct.  The addition of this simple void pointer allows one to map any
> and all request execution caller the facility to search for a specific
> operation without having to run in circles.  Hunting for these details
> over the global device list of all HBA's is silly and one of the key
> reasons why there error recovery path is so painful.
>
>
> Scsi_Request    *req = sc_cmd->sc_request;
> blah_blah_t     *trace = NULL;
>
> trace = (blah_blah_t *)req->trace_ptr;
>
>
> Therefore the specific transport invoking operations via the midlayer will
> have the ablity to track and trace any operation.
>
> It will save everyone headaches.
>
> Cheers,
>
>
> Andre Hedrick, CTO & Founder
> iSCSI Software Solutions Provider
> http://www.PyXTechnologies.com/
>
>
> ------------------------------------------------------------------------
>
> --- linux/drivers/scsi/scsi.h.orig	2002-10-31 01:45:39.000000000 -0800
> +++ linux/drivers/scsi/scsi.h	2002-10-31 01:46:31.000000000 -0800
> @@ -667,8 +667,11 @@
>  	unsigned short sr_sglist_len;	/* size of malloc'd scatter-gather list */
>  	unsigned sr_underflow;	/* Return error if less than
>  				   this amount is transferred */
> +	void *trace_ptr;	/* capable of cmd-cmnd-error tracing */


ok


>  };
>
> +#define MODIFIED_SCSI_H


This falls into C style :)  Instead of this I would do

	#define HAVE_TRACE_PTR 1

just like we already do HAVE_xxx in include/linux/netdevice.h and other 
places.

	Jeff




  reply	other threads:[~2002-11-19  6:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18 23:45 2.5.48 /proc/scsi directory missing Douglas Gilbert
2002-11-19  1:14 ` Patrick Mansfield
2002-11-19  6:16   ` linux-2.4.18-modified-scsi-h.patch Andre Hedrick
2002-11-19  6:28     ` Jeff Garzik [this message]
2002-11-19  6:42       ` linux-2.4.18-modified-scsi-h.patch Andre Hedrick
2002-11-19 10:11     ` linux-2.4.18-modified-scsi-h.patch Douglas Gilbert
2002-11-19 12:16       ` linux-2.4.18-modified-scsi-h.patch Andre Hedrick
2002-11-19 18:40       ` linux-2.4.18-modified-scsi-h.patch Patrick Mansfield
2002-11-19 18:48         ` linux-2.4.18-modified-scsi-h.patch Andre Hedrick
2002-11-19 18:47     ` linux-2.4.18-modified-scsi-h.patch Jeff Garzik
2002-11-19 18:50       ` linux-2.4.18-modified-scsi-h.patch Andre Hedrick

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=3DD9DA23.1070102@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=andre@pyxtechnologies.com \
    --cc=dougg@torque.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@transmeta.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.