From: Dan Williams <firstname.lastname@example.org> To: Goldwyn Rodrigues <email@example.com> Cc: Matthew Wilcox <firstname.lastname@example.org>, Jerome Glisse <email@example.com>, Michal Hocko <firstname.lastname@example.org>, email@example.com, linux-xfs <firstname.lastname@example.org>, linux-fsdevel <email@example.com>, linux-ext4 <firstname.lastname@example.org>, Linux Kernel Mailing List <email@example.com>, linux-nvdimm <firstname.lastname@example.org> Subject: Re: [Lsf-pc] [LSF/MM TOPIC] The end of the DAX experiment Date: Thu, 6 Jun 2019 23:00:35 -0700 Message-ID: <CAPcyv4gZSsAA+GE9otf=WfKSkGMcTbxgdgSCErNys4sOCdCzuA@mail.gmail.com> (raw) In-Reply-To: <20190605162204.jzou5hry5exly5wx@fiona> On Wed, Jun 5, 2019 at 9:22 AM Goldwyn Rodrigues <email@example.com> wrote: > > Hi Dan/Jerome, > > On 12:20 14/02, Dan Williams wrote: > > On Thu, Feb 14, 2019 at 12:09 PM Matthew Wilcox <firstname.lastname@example.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 <email@example.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. Half joking, but I was hoping that by the time I had circled back to finally reviewing the brtfs dax patches that a solution to this problem would be waiting. We spent more time on other DAX topics. I recall that Jerome and I were mutually skeptical of each others approaches at first glance, but we did not get into the details. So, I think it will be a matter of getting the idea coded up. I'm finally coming out from under a pile of mm work so I should have some time this cycle to push the page proxy idea forward.
next prev parent reply index Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-06 21:12 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 2019-06-07 6:00 ` Dan Williams [this message] 2019-02-17 20:29 ` Ric Wheeler 2019-02-18 18:17 ` Dan Williams
Reply instructions: You may reply publically 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='CAPcyv4gZSsAA+GE9otf=WfKSkGMcTbxgdgSCErNys4sOCdCzuA@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
Linux-Fsdevel Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-fsdevel/0 linux-fsdevel/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-fsdevel linux-fsdevel/ https://lore.kernel.org/linux-fsdevel \ email@example.com firstname.lastname@example.org public-inbox-index linux-fsdevel Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-fsdevel AGPL code for this site: git clone https://public-inbox.org/ public-inbox