From: Boaz Harrosh <openosd@gmail.com>
To: Dan Williams <dan.j.williams@intel.com>,
Michal Hocko <mhocko@kernel.org>
Cc: 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: Mon, 9 Dec 2019 18:20:24 +0200 [thread overview]
Message-ID: <5a45a763-d060-7cb1-9772-dd6e9f5f868a@gmail.com> (raw)
In-Reply-To: <CAPcyv4gxFKBQ9eVdn+pNEzBXRfw6Qwfmu21H2i5uj-PyFmRAGQ@mail.gmail.com>
On 14/02/2019 20:25, Dan Williams wrote:
> On Thu, Feb 14, 2019 at 5:46 AM Michal Hocko <mhocko@kernel.org> 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.
>
This topic is very interesting to me.
In current ZUFS implementation we support this option for a long time.
IE: Map same pte_t into different indexes of the same file-mappings as well as
in vma(s) of different files, at different indexes. Including invalidation
of mapping of a pwrite into such a shared page.
(A write to a shared block will allocate a new block for writing)
This effort off-course involves the participation of the FileSystem
to give a list of files and indexes for map_unmapping().
I can explain if you want how we did this.
Cheers
Boaz
next prev parent reply other threads:[~2019-12-09 16:20 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
2019-06-07 6:00 ` Dan Williams
2019-12-09 16:20 ` Boaz Harrosh [this message]
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=5a45a763-d060-7cb1-9772-dd6e9f5f868a@gmail.com \
--to=openosd@gmail.com \
--cc=dan.j.williams@intel.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 \
/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).