Date: Thu, 16 Jan 2020 13:39:00 -0500 From: Vivek Goyal Message-ID: <20200116183900.GC25291@redhat.com> References: <20200109112447.GG27035@quack2.suse.cz> <20200114203138.GA3145@redhat.com> <20200114212805.GB3145@redhat.com> <20200115195617.GA4133@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Virtio-fs] [PATCH 01/19] dax: remove block device dependencies List-Id: Development discussions about virtio-fs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Dan Williams Cc: virtio-fs@redhat.com, Jan Kara , Miklos Szeredi , "Darrick J. Wong" , Dave Chinner , Linux Kernel Mailing List , Christoph Hellwig , linux-nvdimm , Jeff Moyer , linux-fsdevel On Thu, Jan 16, 2020 at 10:09:46AM -0800, Dan Williams wrote: > On Wed, Jan 15, 2020 at 1:08 PM Jeff Moyer wrote: > > > > Hi, Dan, > > > > Dan Williams writes: > > > > > I'm going to take a look at how hard it would be to develop a kpartx > > > fallback in udev. If that can live across the driver transition then > > > maybe this can be a non-event for end users that already have that > > > udev update deployed. > > > > I just wanted to remind you that label-less dimms still exist, and are > > still being shipped. For those devices, the only way to subdivide the > > storage is via partitioning. > > True, but if kpartx + udev can make this transparent then I don't > think users lose any functionality. They just gain a device-mapper > dependency. So udev rules will trigger when a /dev/pmemX device shows up and run kpartx which in turn will create dm-linear devices and device nodes will show up in /dev/mapper/pmemXpY. IOW, /dev/pmemXpY device nodes will be gone. So if any of the scripts or systemd unit files are depenent on /dev/pmemXpY, these will still be broken out of the box and will have to be modified to use device nodes in /dev/mapper/ directory instead. Do I understand it right, Or I missed the idea completely. Vivek