From: Dan Williams <email@example.com> To: Jerome Glisse <firstname.lastname@example.org> Cc: Michal Hocko <email@example.com>, firstname.lastname@example.org, linux-xfs <email@example.com>, linux-fsdevel <firstname.lastname@example.org>, linux-ext4 <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org>, linux-nvdimm <email@example.com> Subject: Re: [Lsf-pc] [LSF/MM TOPIC] The end of the DAX experiment Date: Thu, 14 Feb 2019 11:31:24 -0800 Message-ID: <CAPcyv4jLTdJyTOy715qvBL_j_deiLoBmu_thkUnFKZKMvZL6hA@mail.gmail.com> (raw) In-Reply-To: <20190214191013.GA3420@redhat.com> On Thu, Feb 14, 2019 at 11:10 AM Jerome Glisse <firstname.lastname@example.org> wrote: > > On Thu, Feb 14, 2019 at 10:25:07AM -0800, Dan Williams wrote: > > On Thu, Feb 14, 2019 at 5:46 AM Michal Hocko <email@example.com> wrote: > > > > > > On Wed 06-02-19 13:12:59, Dan Williams wrote: > > > [...] > > > > * Userfaultfd for file-backed mappings and DAX > > > > > > I assume that other topics are meant to be FS track but this one is MM, > > > right? > > > > Yes, but I think it is the lowest priority of all the noted sub-topics > > in this proposal. The DAX-reflink discussion, where a given > > physical-page may need to be mapped into multiple inodes at different > > offsets, might be more fruitful to have as a joint discussion with MM. > > Note that my generic page write protection work can be use for that ie > having a single page correspond to multiple different mapping with also > different offset within each mapping. While in my patchset i only solve > the mapping aliasing issue, the index can be solve in much the same way > because same thinking apply. Namely that when you work on a file you > know the mapping and file offset and thus the index and when you work on > the vma you know the mapping and offset within the vma which translate > to offset within the file. They are only few places that do not have the > informations available and those do not care about it. > > 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.
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 [this message] 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 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=CAPcyv4jLTdJyTOy715qvBL_j_deiLoBmu_thkUnFKZKMvZL6hA@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 \ /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