Re: [ANNOUNCE] Status of unlocked_qcmds=1 operation for .37

[James Bottomley]

On Tue, 2010-10-26 at 16:00 -0700, Nicholas A. Bellinger wrote:
> On Tue, 2010-10-26 at 22:50 +0000, James Bottomley wrote:
> > On Tue, 2010-10-26 at 15:34 -0700, Nicholas A. Bellinger wrote:
> > > On Tue, 2010-10-26 at 17:27 -0500, James Bottomley wrote:
> > > > On Tue, 2010-10-26 at 15:08 -0700, Nicholas A. Bellinger wrote:
> > > > > [PATCH] scsi: Add SCSI_EH_SOFTIRQ_DONE usage
> > > > > 
> > > > > This patch introduces a SCSI_EH_SOFTIRQ_DONE flag that is set in scsi_softirq_done()
> > > > > from block soft_irq context that is used to signal when scsi_try_to_abort_cmd() should
> > > > > be calling __scsi_try_to_abort_cmd() for a timed out struct scsi_cmnd instead of
> > > > > returning SUCCESS via checking only blk_test_rq_complete().  This is done because
> > > > > blk_rq_timed_out_timer() calls blk_mark_rq_complete() before blk_rq_timed_out() ->
> > > > > struct request_queue->rq_timed_out_fn().
> > > > 
> > > > This is getting pretty far off into the weeds.  I think the first step
> > > > should be queue lock push down into ->queuecommand.  This would still
> > > > necessitate locking around the serial number.
> > > 
> > > Hmmm, I am not sure I understand what you mean here.  My understanding
> > > is that the whole point of the series was to remove any locking around
> > > the serial number in order to make scsi_dispatch_cmd() lockless,
> > > right..?
> > 
> > The point is that several things have to happen for that to be a
> > reality.  The easiest and most obvious thing is lock push down in
> > ->queuecommand.
> > 
> 
> Ok, can you please explain to me what you mean here..?  As I really
> thought we came to consensus that:
> 
> *) running in unlocked_qcmd=1 was to be made the default for LLDs using
> the legacy optimization of ->queuecommand() -> unlock() ->
> do_some_lld_work() -> lock() -> return to scsi_dispatch_cmd()

So I was thinking no flag for changing locking behaviour ... simply push
the lock down into the ->queuecommand routines that need it, like we did
for the error handler.

James

> *) For the mpt-fusion / mpt2sas drivers which did not use the legacy
> optimization, but Tim Chen has tested with the former and I am awaiting
> an ACK from LSI on the latter.
> 
> *) All other drivers will function with host_lock held (eg: legacy mode)
> in scsi_dispatch_cmd().
> 
> *) All drivers using cmd->serial_number for anything beyond an
> informational purpose converted to use scsi_cmd_get_serial().
> 
> > The next is most likely serial number elimination.
> > 
> > But the point is that we don't have to do the whole thing all at once
> > (and spend months trying to get the series right).
> 
> Not exactly correct, we have the whole thing ready right now with libfc
> running unlocked_qcmd=0 legacy mode.
> 
> Once I verify START_STOP case in scsi_error.c, I am happy to respin a
> mergeable tree from linus HEAD for you to pull ASAP.
> 
> > 
> > > That is what the current patch series already does, in that it makes the
> > > use of cmd->serial_number optional and requires LLDs who use this for
> > > anything beyond an informational purpose to explictly call
> > > scsi_cmd_get_serial(). 
> > 
> > OK, so this patch is a corner case where the error handler is using the
> > serial number value to deduce something the block layer already knows
> > (whether the command completed or not). I don't think introducing a
> > substitute flag is the right way, the information should just be
> > extracted properly.
> > 
> 
> Well, according to andmike this is two corner cases that are a result of
> the drop-host_lock-v4 series using only blk_test_rq_complete() in
> scsi_try_to_abort_cmd(), which will be true because of:
> 
> blk_rq_timed_out_timer() ->  blk_mark_rq_complete()
> 
> > But arguments about this don't have to impede the lock push down.
> > 
> 
> Sure, but I assume you mean the lock push down only for the legacy LLDs
> that are not already internally unlocking host_lock in
> SHT->queuecommand() in mainline code right..?  
> 
> --nab
> 
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/