[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4FA0BE55.2000305@cs.wisc.edu>
Date: Tue, 01 May 2012 23:55:49 -0500
From: Mike Christie <michaelc@...wisc.edu>
To: Tejun Heo <tj@...nel.org>
CC: axboe@...nel.dk, vgoyal@...hat.com, ctalbott@...gle.com,
rni@...gle.com, linux-kernel@...r.kernel.org,
cgroups@...r.kernel.org, containers@...ts.linux-foundation.org,
fengguang.wu@...el.com, hughd@...gle.com,
akpm@...ux-foundation.org,
James Bottomley <James.Bottomley@...senPartnership.com>,
James Smart <james.smart@...lex.com>
Subject: Re: [PATCH 05/11] block: drop custom queue draining used by scsi_transport_{iscsi|fc}
On 04/26/2012 04:59 PM, Tejun Heo wrote:
> iscsi_remove_host() uses bsg_remove_queue() which implements custom
> queue draining. fc_bsg_remove() open-codes mostly identical logic.
>
> The draining logic isn't correct in that blk_stop_queue() doesn't
> prevent new requests from being queued - it just stops processing, so
> nothing prevents new requests to be queued after the logic determines
> that the queue is drained.
>
> blk_cleanup_queue() now implements proper queue draining and these
> custom draining logics aren't necessary. Drop them and use
> bsg_unregister_queue() + blk_cleanup_queue() instead.
>
> Signed-off-by: Tejun Heo <tj@...nel.org>
> Cc: James Bottomley <James.Bottomley@...senPartnership.com>
> Cc: Mike Christie <michaelc@...wisc.edu>
> Cc: James Smart <james.smart@...lex.com>
> ---
> block/bsg-lib.c | 53 -----------------------------------
> drivers/scsi/scsi_transport_fc.c | 38 -------------------------
> drivers/scsi/scsi_transport_iscsi.c | 2 +-
iSCSI changes worked ok for me. I replicated the problem that the old
code was supposed to fix and verified the new code worked ok. I also
tested the FC code briefly (I do not have a proper setup to really
stress it), and it worked ok.
Thanks for killing that code for us.
Reviewed-by: Mike Christie <michaelc@....wisc.edu>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists