From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933252Ab0EKGzZ (ORCPT ); Tue, 11 May 2010 02:55:25 -0400 Received: from 0122700014.0.fullrate.dk ([95.166.99.235]:33587 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933045Ab0EKGzW (ORCPT ); Tue, 11 May 2010 02:55:22 -0400 Date: Tue, 11 May 2010 08:55:20 +0200 From: Jens Axboe To: Mike Snitzer Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org, Kiyoshi Ueda , "Jun'ichi Nomura" , Vivek Goyal Subject: Re: [RFC PATCH 1/2] block: allow initialization of previously allocated request_queue Message-ID: <20100511065520.GK27497@kernel.dk> References: <1273532139-23043-1-git-send-email-snitzer@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1273532139-23043-1-git-send-email-snitzer@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. -- Jens Axboe