[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211104173417.GJ2237511@magnolia>
Date: Thu, 4 Nov 2021 10:34:17 -0700
From: "Darrick J. Wong" <djwong@...nel.org>
To: Christoph Hellwig <hch@....de>
Cc: Eric Sandeen <sandeen@...deen.net>,
Dan Williams <dan.j.williams@...el.com>,
Mike Snitzer <snitzer@...hat.com>,
Ira Weiny <ira.weiny@...el.com>, dm-devel@...hat.com,
linux-xfs@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-s390@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-erofs@...ts.ozlabs.org, linux-ext4@...r.kernel.org,
virtualization@...ts.linux-foundation.org
Subject: Re: futher decouple DAX from block devices
On Thu, Nov 04, 2021 at 09:17:40AM +0100, Christoph Hellwig wrote:
> On Wed, Nov 03, 2021 at 12:59:31PM -0500, Eric Sandeen wrote:
> > Christoph, can I ask what the end game looks like, here? If dax is completely
> > decoupled from block devices, are there user-visible changes?
>
> Yes.
>
> > If I want to
> > run fs-dax on a pmem device - what do I point mkfs at, if not a block device?
>
> The rough plan is to use the device dax character devices. I'll hopefully
> have a draft version in the next days.
/me wonders, are block devices going away? Will mkfs.xfs have to learn
how to talk to certain chardevs? I guess jffs2 and others already do
that kind of thing... but I suppose I can wait for the real draft to
show up to ramble further. ;)
--D
Powered by blists - more mailing lists