linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: [LSF/MM TOPIC] Persistent Memory
Date: Fri, 20 Dec 2013 10:05:02 -0700	[thread overview]
Message-ID: <20131220170502.GF19166@parisc-linux.org> (raw)


I should like to discuss the current situation with Linux support for
persistent memory.  While I expect the current discussion to be long
over by March, I am certain that there will be topics around persistent
memory that have not been settled at that point.

I believe this will mostly be of crossover interest between filesystem
and MM people, and of lesser interest to storage people (since we're
basically avoiding their code).

Subtopics might include
 - Using persistent memory for FS metadata
   (The XIP code provides persistent memory to userspace.  The filesystem
    still uses BIOs to fetch its metadata)
 - Supporting PMD/PGD mappings for userspace
   (Not only does the filesystem have to avoid fragmentation to make this
    happen, the VM code has to permit these giant mappings)
 - Persistent page cache
   (Another way to take advantage of persstent memory would be to place it
    in the page cache.  But we don't have struct pages for it!  What to do?)
 - Making XIP and non-XIP codepaths closer to each other
   (I think we have a good start on this, but more is needed)

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

             reply	other threads:[~2013-12-20 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 17:05 Matthew Wilcox [this message]
2014-01-08 15:42 ` [Lsf-pc] [LSF/MM TOPIC] Persistent Memory Mel Gorman
2014-01-09  1:35   ` Bob Liu
2014-01-09 10:37     ` Mel Gorman

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=20131220170502.GF19166@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.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).