From: Boaz Harrosh <boaz@plexistor.com>
To: Christoph Hellwig <hch@lst.de>, Yigal Korman <yigal@plexistor.com>
Cc: linux-nvdimm@lists.01.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Matthew Wilcox <matthew.r.wilcox@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [Linux-nvdimm] [GIT PULL] PMEM driver for v4.1
Date: Tue, 14 Apr 2015 09:41:25 +0300 [thread overview]
Message-ID: <552CB695.2020805@plexistor.com> (raw)
In-Reply-To: <20150413171907.GB14243@lst.de>
On 04/13/2015 08:19 PM, Christoph Hellwig wrote:
> On Mon, Apr 13, 2015 at 02:11:56PM +0300, Yigal Korman wrote:
>> mlock()
>
> DAX files always are in-memory so this just sounds like an oversight.
> method.
Yes mlock on DAX can just return true, but mlock implies MAP_POPULATE.
Which means "I would like to page-fault the all mmap range at mmap time
so at access time I'm guarantied not to sleep". This is usually done
for latency sensitive applications.
But current code fails on MAP_POPULATE for DAX because it is only
implemented for pages, and therefor mlock fails as well.
One thing I do not understand. does mlock also protects against
truncate?
Thanks
Boaz
next prev parent reply other threads:[~2015-04-14 6:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 9:33 [GIT PULL] PMEM driver for v4.1 Ingo Molnar
2015-04-13 9:35 ` Christoph Hellwig
2015-04-13 10:45 ` Ingo Molnar
2015-04-13 11:11 ` [Linux-nvdimm] " Yigal Korman
2015-04-13 17:19 ` Christoph Hellwig
2015-04-14 6:41 ` Boaz Harrosh [this message]
2015-04-13 12:21 ` Boaz Harrosh
2015-04-13 12:35 ` Ingo Molnar
2015-04-13 13:36 ` Boaz Harrosh
2015-04-13 17:22 ` Christoph Hellwig
2015-04-13 17:18 ` Christoph Hellwig
2015-04-14 12:41 ` Ingo Molnar
2015-04-14 13:45 ` Boaz Harrosh
2015-04-14 14:08 ` [Linux-nvdimm] " Elliott, Robert (Server Storage)
2015-04-14 16:34 ` Dan Williams
2015-04-14 21:46 ` Elliott, Robert (Server Storage)
2015-04-15 8:03 ` Ingo Molnar
2015-04-14 16:04 ` Dan Williams
2015-04-15 8:45 ` Ingo Molnar
2015-04-16 4:31 ` Dan Williams
2015-04-17 6:38 ` Christoph Hellwig
2015-04-18 15:42 ` Linus Torvalds
2015-05-25 18:16 ` [Linux-nvdimm] " Matthew Wilcox
2015-05-25 18:30 ` Ingo Molnar
2015-05-26 8:41 ` Boaz Harrosh
2015-05-26 19:31 ` Matthew Wilcox
2015-05-27 8:10 ` Boaz Harrosh
2015-05-27 8:11 ` Christoph Hellwig
2015-05-27 8:26 ` Boaz Harrosh
2015-05-27 7:50 ` Ingo Molnar
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=552CB695.2020805@plexistor.com \
--to=boaz@plexistor.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=matthew.r.wilcox@intel.com \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yigal@plexistor.com \
/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).