From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Snitzer Subject: Re: [RFC PATCH 1/2] block: allow initialization of previously allocated request_queue Date: Tue, 11 May 2010 09:18:56 -0400 Message-ID: <20100511131856.GB25211@redhat.com> References: <1273532139-23043-1-git-send-email-snitzer@redhat.com> <20100511065520.GK27497@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20100511065520.GK27497@kernel.dk> Sender: linux-kernel-owner@vger.kernel.org To: Jens Axboe Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org, Kiyoshi Ueda , Jun'ichi Nomura , Vivek Goyal , Nikanth Karthikesan List-Id: dm-devel.ids On Tue, May 11 2010 at 2:55am -0400, Jens Axboe wrote: > On Mon, May 10 2010, Mike Snitzer wrote: > > blk_init_queue() allocates the request_queue structure and then > > initializes it as needed (request_fn, elevator, etc). > > > > Split initialization out to blk_init_allocated_queue_node. > > Introduce blk_init_allocated_queue wrapper function to model existing > > blk_init_queue and blk_init_queue_node interfaces. > > > > Export elv_register_queue to allow a newly added elevator to be > > registered with sysfs. Export elv_unregister_queue for symmetry. > > > > These changes allow DM to initialize a device's request_queue with more > > precision. In particular, DM no longer unconditionally initializes a > > full request_queue (elevator et al). It only does so for a > > request-based DM device. > > Looks good, I'll apply this. I don't think the exports need to be _GPL > in this case, generally I've only done that with the exports for hooking > in a new IO scheduler. OK, thanks for picking this up. Do you want me to send v2 that drops the _GPL or will you make those changes? Mike