From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Jerome Glisse <jglisse@redhat.com>,
Michal Hocko <mhocko@kernel.org>,
lsf-pc@lists.linux-foundation.org,
linux-xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] The end of the DAX experiment
Date: Wed, 5 Jun 2019 11:22:04 -0500 [thread overview]
Message-ID: <20190605162204.jzou5hry5exly5wx@fiona> (raw)
In-Reply-To: <CAPcyv4hsDqvrV5yiDq8oWPuWb3WpuCEk_HB4qBxfiDpUwo75QQ@mail.gmail.com>
Hi Dan/Jerome,
On 12:20 14/02, Dan Williams wrote:
> On Thu, Feb 14, 2019 at 12:09 PM Matthew Wilcox <willy@infradead.org> wrote:
> >
> > On Thu, Feb 14, 2019 at 11:31:24AM -0800, Dan Williams wrote:
> > > On Thu, Feb 14, 2019 at 11:10 AM Jerome Glisse <jglisse@redhat.com> wrote:
> > > > I am just again working on my struct page mapping patchset as well as
> > > > the generic page write protection that sits on top. I hope to be able
> > > > to post the v2 in couple weeks. You can always look at my posting last
> > > > year to see more details.
> > >
> > > Yes, I have that in mind as one of the contenders. However, it's not
> > > clear to me that its a suitable fit for filesystem-reflink. Others
> > > have floated the 'page proxy' idea, so it would be good to discuss the
> > > merits of the general approaches.
> >
> > ... and my preferred option of putting pfn entries in the page cache.
>
> Another option to include the discussion.
>
> > Or is that what you meant by "page proxy"?
>
> Page proxy would be an object that a filesystem could allocate to
> point back to a single physical 'struct page *'. The proxy would
> contain an override for page->index.
Was there any outcome on this and its implementation? I am specifically
interested in this for DAX support on btrfs/CoW: The TODO comment on
top of dax_associate_entry() :)
If there are patches/git tree I could use to base my patches on, it would
be nice.
--
Goldwyn
next prev parent reply other threads:[~2019-06-05 16:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 21:12 [LSF/MM TOPIC] The end of the DAX experiment Dan Williams
2019-02-07 21:51 ` Kani, Toshi
2019-02-08 9:02 ` Johannes Thumshirn
2019-02-14 13:46 ` [Lsf-pc] " Michal Hocko
2019-02-14 18:25 ` Dan Williams
2019-02-14 19:10 ` Jerome Glisse
2019-02-14 19:31 ` Dan Williams
2019-02-14 20:08 ` Matthew Wilcox
2019-02-14 20:20 ` Dan Williams
2019-02-14 20:34 ` Jerome Glisse
2019-02-16 5:37 ` Dave Chinner
2019-06-05 16:22 ` Goldwyn Rodrigues [this message]
2019-06-07 6:00 ` Dan Williams
2019-12-09 16:20 ` Boaz Harrosh
2019-02-17 20:29 ` Ric Wheeler
2019-02-18 18:17 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190605162204.jzou5hry5exly5wx@fiona \
--to=rgoldwyn@suse.de \
--cc=dan.j.williams@intel.com \
--cc=jglisse@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).