public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Mike Christie <michaelc@cs.wisc.edu>, Jens Axboe <axboe@suse.de>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] convert the remaining mid-layer pieces to scsi_execute_req
Date: Sat, 11 Jun 2005 14:09:25 -0500	[thread overview]
Message-ID: <1118516965.4924.18.camel@mulgrave> (raw)
In-Reply-To: <20050611185443.GB3406@pentafluge.infradead.org>

On Sat, 2005-06-11 at 19:54 +0100, Jeff Garzik wrote:
> On Sat, Jun 11, 2005 at 10:02:02AM -0500, James Bottomley wrote:
> > After this, we just have some drivers, all the ULDs and the SPI
> > transport class using scsi_wait_req().
> > 
> > James
> > 
> > --- a/drivers/scsi/scsi_ioctl.c
> > +++ b/drivers/scsi/scsi_ioctl.c
> > @@ -88,25 +88,21 @@ static int ioctl_probe(struct Scsi_Host 
> >  static int ioctl_internal_command(struct scsi_device *sdev, char *cmd,
> >  				  int timeout, int retries)
> >  {
> > -	struct scsi_request *sreq;
> >  	int result;
> >  	struct scsi_sense_hdr sshdr;
> > +	char sense[SCSI_SENSE_BUFFERSIZE];
> 
> What is the average stack size at this call depth?

Erm, well that's architecture dependent, as I'm sure you know.

On parisc64, none of the prior callers really goes over a stack frame,
so it's 128*depth.

James



      reply	other threads:[~2005-06-11 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-11 15:02 [PATCH] convert the remaining mid-layer pieces to scsi_execute_req James Bottomley
2005-06-11 18:54 ` Jeff Garzik
2005-06-11 19:09   ` James Bottomley [this message]

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=1118516965.4924.18.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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