public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Patch added to scsi-rc-fixes-2.6:  [SCSI] host lock push-down
Date: Wed, 10 Nov 2010 17:45:58 -0600	[thread overview]
Message-ID: <1289432759.3016.63.camel@mulgrave.site> (raw)
In-Reply-To: <4CDB2A81.5030100@garzik.org>

On Wed, 2010-11-10 at 18:28 -0500, Jeff Garzik wrote:
> On 11/10/2010 05:40 PM, James Bottomley wrote:
> > Your commit:
> >
> >      [SCSI] host lock push-down
> >
> >      Move the mid-layer's ->queuecommand() invocation from being locked
> >      with the host lock to being unlocked to facilitate speeding up the
> >      critical path for drivers who don't need this lock taken anyway.
> >
> >      The patch below presents a simple SCSI host lock push-down as an
> >      equivalent transformation.  No locking or other behavior should change
> >      with this patch.  All existing bugs and locking orders are preserved.
> >
> >      Minimal code disturbance was attempted with this change.  Most drivers
> >      needed only two one-line modifications for their host lock push-down.
> >
> >      Signed-off-by: Jeff Garzik<jgarzik@redhat.com>
> >      Signed-off-by: James Bottomley<James.Bottomley@suse.de>
> >
> > has been added to the upstream SCSI tree
> > You can find it here:
> 
> No comments on renaming ->queuecommand to something else?

What we wondered about doing differently isn't really relevant for a
change log ... that should just really be about what was done (to avoid
confusion).

> The consequences are rather dire if this goes unnoticed, yes?

You mean if there's a missed in-tree driver?  Yes, but I took care to
make sure all SCSI drivers were accounted for.  For out of tree drivers,
as with the eh lock push down, it's caveat emptor.

James



  reply	other threads:[~2010-11-10 23:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201011102240.oAAMe86a001486@hera.kernel.org>
2010-11-10 23:28 ` Patch added to scsi-rc-fixes-2.6: [SCSI] host lock push-down Jeff Garzik
2010-11-10 23:45   ` James Bottomley [this message]
2010-11-10 23:52     ` Jeff Garzik
2010-11-11  8:58       ` Nicholas A. Bellinger

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=1289432759.3016.63.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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