From: Matthew Wilcox <willy@linux.intel.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NVM Mapping API
Date: Wed, 16 May 2012 12:02:36 -0400 [thread overview]
Message-ID: <20120516160236.GI22985@linux.intel.com> (raw)
In-Reply-To: <4FB2E069.7060703@amacapital.net>
On Tue, May 15, 2012 at 04:02:01PM -0700, Andy Lutomirski wrote:
> I would love to use this from userspace. If I could carve out a little
> piece of NVM as a file (or whatever) and mmap it, I could do all kinds
> of fun things with that. It would be nice if it had well-defined, or at
> least configurable or discoverable, caching properties (e.g. WB, WT, WC,
> UC, etc.).
Yes, usage from userspace is definitely planned; again through a
filesystem interface. Treating it like a regular file will work as
expected; the question is how to expose the interesting properties
(eg is there a lighter weight mechanism than calling msync()).
My hope was that by having a discussion of how to use this stuff within
the kernel, we might come up with some usage models that would inform
how we design a user space library.
> (Even better would be a way to make a clone of an fd that only allows
> mmap, but that's a mostly unrelated issue.)
O_MMAP_ONLY? And I'm not sure why you'd want to forbid reads and writes.
next prev parent reply other threads:[~2012-05-16 16:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 13:34 NVM Mapping API Matthew Wilcox
2012-05-15 17:46 ` Greg KH
2012-05-16 15:57 ` Matthew Wilcox
2012-05-18 12:07 ` Marco Stornelli
2012-05-15 23:02 ` Andy Lutomirski
2012-05-16 16:02 ` Matthew Wilcox [this message]
2012-05-31 17:53 ` Andy Lutomirski
2012-05-16 6:24 ` Vyacheslav Dubeyko
2012-05-16 16:10 ` Matthew Wilcox
2012-05-17 9:06 ` Vyacheslav Dubeyko
2012-05-16 21:58 ` Benjamin LaHaise
2012-05-17 19:06 ` Matthew Wilcox
2012-05-16 9:52 ` James Bottomley
2012-05-16 17:35 ` Matthew Wilcox
2012-05-16 19:58 ` Christian Stroetmann
2012-05-19 22:19 ` Christian Stroetmann
2012-05-17 9:54 ` James Bottomley
2012-05-17 18:59 ` Matthew Wilcox
2012-05-18 9:03 ` James Bottomley
2012-05-18 10:13 ` Boaz Harrosh
2012-05-18 14:49 ` Matthew Wilcox
2012-05-18 15:08 ` Alan Cox
2012-05-18 15:31 ` James Bottomley
2012-05-18 17:19 ` Matthew Wilcox
2012-05-16 13:04 ` Boaz Harrosh
2012-05-16 18:33 ` Matthew Wilcox
2012-05-18 9:33 ` Arnd Bergmann
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=20120516160236.GI22985@linux.intel.com \
--to=willy@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/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).