From: Andy Lutomirski <luto@amacapital.net>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: [LSF/MM TOPIC] [ATTEND] Persistent memory
Date: Thu, 16 Jan 2014 16:56:50 -0800 [thread overview]
Message-ID: <CALCETrUaotUuzn60-bSt1oUb8+94do2QgiCq_TXhqEHj79DePQ@mail.gmail.com> (raw)
I'm interested in a persistent memory track. There seems to be plenty
of other emails about this, but here's my take:
First, I'm not an FS expert. I've never written an FS, touched an
on-disk (or on-persistent-memory) FS format. I have, however, mucked
with some low-level x86 details, and I'm a heavy abuser of the Linux
page cache.
I'm an upcoming user of persistent memory -- I have some (in the form
if NV-DIMMs) and I have an application (HFT and a memory-backed
database thing) that I'll port to run on pmfs or ext4 w/ XIP once
everything is ready.
I'm also interested in some of the implementation details. For this
stuff to be reliable on anything resembling commodity hardware, there
will be some caching issues to deal with. For example, I think it
would be handy to run things like pmfs on top of write-through
mappings. This is currently barely supportable (and only using
mtrrs), but it's not terribly complicated (on new enough hardware) to
support real write-through PAT entries.
I've written an i2c-imc driver (currently in limbo on the i2c list),
which will likely be used for control operations on NV-DIMMs plugged
into Intel-based server boards.
In principle, I could even bring a working NV-DIMM system to the
summit -- it's nearby, and this thing isn't *that* large :)
--Andy
--
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 reply other threads:[~2014-01-17 0:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 0:56 Andy Lutomirski [this message]
2014-01-17 4:17 ` Howard Chu
2014-01-17 19:22 ` Andy Lutomirski
2014-01-21 7:38 ` Howard Chu
2014-01-21 11:17 ` [Lsf-pc] " Dave Chinner
2014-01-21 13:57 ` Howard Chu
2014-01-21 20:20 ` Dave Chinner
2014-01-21 16:48 ` Andy Lutomirski
2014-01-21 20:36 ` Dave Chinner
2014-01-21 20:59 ` Andy Lutomirski
2014-01-21 23:03 ` Dave Chinner
2014-01-21 23:22 ` Andy Lutomirski
2014-01-22 8:13 ` Howard Chu
2014-01-23 19:54 ` Andy Lutomirski
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=CALCETrUaotUuzn60-bSt1oUb8+94do2QgiCq_TXhqEHj79DePQ@mail.gmail.com \
--to=luto@amacapital.net \
--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