From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Subject: Re: gendisk and lightnvm To: Dan Williams References: <5742B023.2040503@bjorling.me> <57473C2D.2060700@bjorling.me> <57476FC1.6020702@bjorling.me> Cc: Jens Axboe , Christoph Hellwig , Keith Busch , Simon Lund , linux-block@vger.kernel.org From: =?UTF-8?Q?Matias_Bj=c3=b8rling?= Message-ID: <57488327.8080104@bjorling.me> Date: Fri, 27 May 2016 19:25:59 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed List-ID: On 05/27/2016 12:06 AM, Dan Williams wrote: > On Thu, May 26, 2016 at 2:50 PM, Matias Bjørling wrote: >> On 05/26/2016 09:05 PM, Dan Williams wrote: > [..] >> In that case, the holder kobject is maintained by the request queue. That >> moves the block device naming earlier in the initialization process, and the >> request queue would properly need to hold the (struct gendisk)->diskname. I >> wonder if there is a better way. > > I don't see why it is necessary to move the block device naming > earlier. The block device kobject can link to the mq/ kobject created > by lightnvm rather than include it as a child of the gendisk. > You're right. I'll cook up some RFC patches with the changes. Thanks.