public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>,
	James Bottomley <James.Bottomley@suse.de>,
	Christoph Hellwig <hch@lst.de>,
	Mike Christie <michaelc@cs.wisc.edu>,
	Ravi Anand <ravi.anand@qlogic.com>,
	Andrew Vasquez <andrew.vasquez@qlogic.com>,
	Joe Eykholt <jeykholt@cisco.com>,
	James Smart <james.smart@emulex.com>,
	Vasu Dev <vasu.dev@linux.intel.com>,
	Tim Chen <tim.c.chen@linux.intel.com>,
	Andi Kleen <ak@linux.intel.com>, Tejun Heo <tj@kernel.org>,
	Mike Anderson <andmike@linux.vnet.ibm.com>,
	MPTFusionLinux <DL-MPTFusionLinux@lsi.com>
Subject: Re: [PATCH 04/11] libsas: Convert to host_lock less w/ interrupts disabled externally
Date: Wed, 17 Nov 2010 14:36:11 -0800	[thread overview]
Message-ID: <1290033371.31890.66.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20101117223053.GB26760@infradead.org>

On Wed, 2010-11-17 at 17:30 -0500, Christoph Hellwig wrote:
> > @@ -189,7 +189,7 @@ int sas_queue_up(struct sas_task *task)
> >   * Note: XXX: Remove the host unlock/lock pair when SCSI Core can
> >   * call us without holding an IRQ spinlock...
> 
> That comment can be removed now.
> 
> >   */
> > -static int sas_queuecommand_lck(struct scsi_cmnd *cmd,
> 
> That's now how the code looks like upstream.
> 
> > +static int sas_queuecommand_irq_disable(struct scsi_cmnd *cmd,
> >  		     void (*scsi_done)(struct scsi_cmnd *))
> >  	__releases(host->host_lock)
> >  	__acquires(dev->sata_dev.ap->lock)
> 
> The host_lock annotations are not incorrect, and the sata_dev ones
> never made sense.
> 
> > @@ -254,7 +254,7 @@ out:
> >  	return res;
> >  }
> >  
> > -DEF_SCSI_QCMD(sas_queuecommand)
> > +IRQ_DISABLE_SCSI_QCMD(sas_queuecommand)
> 
> And in addition this doesn't even seem correct to me.  First thing
> sas_queuecommand upstream does is spin_unlock_irq on the host_lock
> which it expects to be held, then it does a spin_lock_irqsave for the
> sata case, or operations that do not appear to need a lock for the
> sas case.

Ugh, this was the one patch that I carried forwad and had to apply by
hand, and evidently I missed the some bits.  Pushing this commit now..

Thanks,

>From 444d87126389286c869d10c947707c1d33855995 Mon Sep 17 00:00:00 2001
From: Nicholas Bellinger <nab@linux-iscsi.org>
Date: Wed, 17 Nov 2010 22:38:23 +0000
Subject: [PATCH] libsas: Added dropped bits for host_lock-less operation

This patch fixes drop-lock_less usage, lockdep annotation, and comment
changes that where dropped while moving the libsas forward.

Signed-off-by: Nicholas A. Bellinger <nab@linux-iscsi.org>
Reported-by: Christoph Hellwig <hch@lst.de>
---
 drivers/scsi/libsas/sas_scsi_host.c |    8 --------
 1 files changed, 0 insertions(+), 8 deletions(-)

diff --git a/drivers/scsi/libsas/sas_scsi_host.c
b/drivers/scsi/libsas/sas_scsi_host.c
index 595ed21..011580f 100644
--- a/drivers/scsi/libsas/sas_scsi_host.c
+++ b/drivers/scsi/libsas/sas_scsi_host.c
@@ -185,24 +185,17 @@ int sas_queue_up(struct sas_task *task)
 /**
  * sas_queuecommand -- Enqueue a command for processing
  * @parameters: See SCSI Core documentation
- *
- * Note: XXX: Remove the host unlock/lock pair when SCSI Core can
- * call us without holding an IRQ spinlock...
  */
 static int sas_queuecommand_irq_disable(struct scsi_cmnd *cmd,
                     void (*scsi_done)(struct scsi_cmnd *))
-       __releases(host->host_lock)
        __acquires(dev->sata_dev.ap->lock)
        __releases(dev->sata_dev.ap->lock)
-       __acquires(host->host_lock)
 {
        int res = 0;
        struct domain_device *dev = cmd_to_domain_dev(cmd);
        struct Scsi_Host *host = cmd->device->host;
        struct sas_internal *i = to_sas_internal(host->transportt);

-       spin_unlock_irq(host->host_lock);
-
        {
                struct sas_ha_struct *sas_ha = dev->port->ha;
                struct sas_task *task;
@@ -250,7 +243,6 @@ static int sas_queuecommand_irq_disable(struct
scsi_cmnd *cmd,
                }
        }
 out:
-       spin_lock_irq(host->host_lock);
        return res;
 }

-- 
1.7.2.3


> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2010-11-17 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 22:18 [PATCH 04/11] libsas: Convert to host_lock less w/ interrupts disabled externally Nicholas A. Bellinger
2010-11-17 22:30 ` Christoph Hellwig
2010-11-17 22:36   ` Nicholas A. Bellinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-12  0:13 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=1290033371.31890.66.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=DL-MPTFusionLinux@lsi.com \
    --cc=James.Bottomley@suse.de \
    --cc=ak@linux.intel.com \
    --cc=andmike@linux.vnet.ibm.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=james.smart@emulex.com \
    --cc=jeff@garzik.org \
    --cc=jeykholt@cisco.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=ravi.anand@qlogic.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=tj@kernel.org \
    --cc=vasu.dev@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