On Fri, Apr 13, 2012 at 01:47:10PM -0700, Tejun Heo wrote: > On Fri, Apr 13, 2012 at 04:44:46PM -0400, Vivek Goyal wrote: > > On Fri, Apr 13, 2012 at 01:37:26PM -0700, Tejun Heo wrote: > > > > [..] > > > blk_cleanup_queue() doesn't use blk_queue_bypass_start() to enter > > > bypass mode. > > > > Oh now elevator_exit() has been moved into blk_release_queue(). But > > problem will still be there, isn't it? During driver init, most likely driver > > is holding last reference of the queue and blk_release_queue() will be called > > in the context of blk_cleanup_queue() causing the overhead? > > Hmmm? blk_cleanup_queue() will put the queue into bypassing mode > without going through synchronize_rcu() and all the following > bypassing operations just inc/decs bypass_depth without any draining > operation. Ok, this is non-obivirious part. The very reason you could do the optimzation of synchronize_rcu(), was the fact that either somebody has already called synchronize_rcu() (first caller of blk_bypass_start()) or we know that it is not needed (as we are instanciating queue and no IO could be going on). But neither seems to be the case here. So to make sure that blkg_lookup() under rcu will see the updated value of queue flag (bypass), are we relying on the fact that caller should see the DEAD flag and not go ahead with blkg_lookup()? If yes, atleast it is not obivious. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
