public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Luben Tuikov <luben_tuikov@adaptec.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC][PATCH] allow sleep inside EH hooks
Date: Fri, 27 May 2005 12:49:25 -0400	[thread overview]
Message-ID: <42974F95.6010603@pobox.com> (raw)
In-Reply-To: <42974E19.9040007@adaptec.com>

Luben Tuikov wrote:
> On 05/27/05 04:36, Jeff Garzik wrote:
> 
>>Christoph Hellwig wrote:
>>
>>>No, hav ing the host_lock only held for ->queuecommand which doesn't
>>>need that locking doesn't make any sense.  An API like the current one
>>
>>
>>It makes a lot of sense:  LLDs are written with the assumption that 
>>paths called from ->queuecommand will not be interrupted by their own 
>>interrupt handler, whereas error handling paths are typically written 
>>with precisely the -opposite- assumption.
>>
>>Removing spin_lock_irq() from queuecommand in SCSI EH causes problems, 
>>and solves nothing.
> 
> 
> scsi_done() itself needs no explicit locking, it is completely reentrant
> and this is a good thing.
> 
> I'd like to see the same thing for queuecommand(), i.e. host_lock be gone.

We can take up that topic once I'm done with sleeping-in-EH project :)

I don't disagree...   but changing the locking for ->queuecommand() is a 
-lot- more invasive, and requires much more care.

I'm also curious to see what others think about removing the host_lock 
acquisition from ->queuecommand() calls.

	Jeff



  reply	other threads:[~2005-05-27 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27  4:32 [RFC][PATCH] allow sleep inside EH hooks Jeff Garzik
2005-05-27  6:40 ` Arjan van de Ven
2005-05-27  7:11 ` Christoph Hellwig
2005-05-27  7:48   ` Jeff Garzik
2005-05-27  7:59     ` Christoph Hellwig
2005-05-27  8:36       ` Jeff Garzik
2005-05-27 16:43         ` Luben Tuikov
2005-05-27 16:49           ` Jeff Garzik [this message]
2005-05-27 17:04             ` James Bottomley
2005-05-27 17:22               ` Christoph Hellwig
2005-05-27 17:23                 ` Jeff Garzik
2005-05-27 17:16             ` Christoph Hellwig

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=42974F95.6010603@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=luben_tuikov@adaptec.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