From: Hugh Dickins <hughd@google.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Matthew Wilcox <matthew@wil.cx>, Hugh Dickins <hughd@google.com>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] persistent transparent large
Date: Tue, 28 Jan 2014 14:24:34 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.11.1401281420010.2562@eggly.anvils> (raw)
In-Reply-To: <1390943052.16253.31.camel@dabdike>
On Tue, 28 Jan 2014, James Bottomley wrote:
>
> Then there's the meta problem of is XIP the right approach. Using
> persistence within the current memory address space as XIP is a natural
> fit for mixed volatile/NV systems, but what happens when they're all NV
> memory? Should we be discussing some VM based handling mechanisms for
> persistent memory?
Yes (but at present there's nothing on the table: is the cupboard bare?)
Sorry, answer devoid of content, but since it's my thread...
Hugh
--
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:[~2014-01-28 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 12:23 [LSF/MM ATTEND] persistent transparent large Hugh Dickins
2014-01-28 19:38 ` Matthew Wilcox
2014-01-28 20:42 ` Hugh Dickins
2014-01-29 1:52 ` Matthew Wilcox
2014-01-28 21:04 ` [Lsf-pc] " James Bottomley
2014-01-28 22:24 ` Hugh Dickins [this message]
2014-01-29 2:39 ` Matthew Wilcox
2014-01-29 23:00 ` James Bottomley
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=alpine.LSU.2.11.1401281420010.2562@eggly.anvils \
--to=hughd@google.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=matthew@wil.cx \
/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).