From: Bob Liu <bob.liu@oracle.com>
To: Mel Gorman <mgorman@suse.de>, Matthew Wilcox <matthew@wil.cx>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] Persistent Memory
Date: Thu, 09 Jan 2014 09:35:45 +0800 [thread overview]
Message-ID: <52CDFCF1.5060107@oracle.com> (raw)
In-Reply-To: <20140108154259.GJ27046@suse.de>
On 01/08/2014 11:42 PM, Mel Gorman wrote:
> On Fri, Dec 20, 2013 at 10:05:02AM -0700, Matthew Wilcox wrote:
>>
>> 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)
>
> The filesystem would also have to correctly align the data on disk. All
> this implies that the underlying device is byte-addressible, similar access
> speeds to RAM and directly accessible from userspace without the kernel
> being involved. Without those conditions, I find it hard to believe that
> TLB pressure dominates access cost. Then again I have no experience with
> the devices or their intended use case so would not mind an education.
>
> However, if you really wanted the device to be accessible like this then
> the shortest solutions (and I want to punch myself for even suggesting
> this) is to extend hugetlbfs to directly access these devices. It's
> almost certainly a bad direction to take though, there would need to be a
> good justification for it. Anything in this direction is pushing usage of
> persistent devices to userspace and the kernel just provides an interface,
> maybe that is desirable maybe not.
>
>> - 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?)
>
I think one potential way is to use persistent memory as a second-level
clean page cache through the cleancache API.
--
Regards,
-Bob
--
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-09 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 17:05 [LSF/MM TOPIC] Persistent Memory Matthew Wilcox
2014-01-08 15:42 ` [Lsf-pc] " Mel Gorman
2014-01-09 1:35 ` Bob Liu [this message]
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=52CDFCF1.5060107@oracle.com \
--to=bob.liu@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=matthew@wil.cx \
--cc=mgorman@suse.de \
/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).