From: Dan Williams <dan.j.williams@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux MM <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH v2 1/4] mm: introduce get_user_pages_longterm
Date: Tue, 21 Nov 2017 15:26:26 -0800 [thread overview]
Message-ID: <CAPcyv4jRqkwdVZrRnMcvAq1OJ0+DpHFQ6yhXhgN-ts1HMF1Nfw@mail.gmail.com> (raw)
In-Reply-To: <20171121150501.d4d811a66444cb5c9cb85bf2@linux-foundation.org>
On Tue, Nov 21, 2017 at 3:05 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
>
> On Tue, 14 Nov 2017 11:56:34 -0800 Dan Williams <dan.j.williams@intel.com> wrote:
>
> > Until there is a solution to the dma-to-dax vs truncate problem it is
> > not safe to allow long standing memory registrations against
> > filesytem-dax vmas. Device-dax vmas do not have this problem and are
> > explicitly allowed.
> >
> > This is temporary until a "memory registration with layout-lease"
> > mechanism can be implemented for the affected sub-systems (RDMA and
> > V4L2).
>
> Sounds like that will be unpleasant. Do we really need it to be that
> complex? Can we get away with simply failing the get_user_pages()
> request? Or are there significant usecases for RDMA and V4L to play
> with DAX memory?
V4L plus DAX is indeed dubious, but RDMA to persistent memory is
something the RDMA community is interested in supporting [1].
[1]: http://www.snia.org/sites/default/files/SDC15_presentations/persistant_mem/ChetDouglas_RDMA_with_PM.pdf
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-21 23:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 19:56 [PATCH v2 0/4] introduce get_user_pages_longterm() Dan Williams
2017-11-14 19:56 ` [PATCH v2 1/4] mm: introduce get_user_pages_longterm Dan Williams
2017-11-21 23:05 ` Andrew Morton
2017-11-21 23:26 ` Dan Williams [this message]
2017-11-21 23:11 ` Andrew Morton
2017-11-14 19:56 ` [PATCH v2 2/4] mm: fail get_vaddr_frames() for filesystem-dax mappings Dan Williams
2017-11-27 16:15 ` Jan Kara
2017-11-27 16:19 ` Dan Williams
2017-11-14 19:56 ` [PATCH v2 3/4] [media] v4l2: disable filesystem-dax mapping support Dan Williams
2017-11-27 16:17 ` Jan Kara
2017-11-14 19:56 ` [PATCH v2 4/4] IB/core: disable memory registration of fileystem-dax vmas 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=CAPcyv4jRqkwdVZrRnMcvAq1OJ0+DpHFQ6yhXhgN-ts1HMF1Nfw@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=stable@vger.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