From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [LSF/MM ATTEND] HMM (heterogeneous memory manager) and GPU
Date: Fri, 29 Jan 2016 11:50:28 +0200 [thread overview]
Message-ID: <20160129095028.GA10767@node.shutemov.name> (raw)
In-Reply-To: <20160128175536.GA20797@gmail.com>
On Thu, Jan 28, 2016 at 06:55:37PM +0100, Jerome Glisse wrote:
> Hi,
>
> I would like to attend LSF/MM this year to discuss about HMM
> (Heterogeneous Memory Manager) and more generaly all topics
> related to GPU and heterogeneous memory architecture (including
> persistent memory).
How is persistent memory heterogeneous?
I thought it's either in the same cache coherency domain (DAX case) or is
not a memory for kernel -- behind block layer.
Do we have yet another option?
--
Kirill A. Shutemov
--
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:[~2016-01-29 9:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 17:55 [LSF/MM ATTEND] HMM (heterogeneous memory manager) and GPU Jerome Glisse
2016-01-29 9:50 ` Kirill A. Shutemov [this message]
2016-01-29 13:35 ` Jerome Glisse
2016-02-01 15:46 ` Aneesh Kumar K.V
2016-02-02 23:03 ` Jerome Glisse
2016-02-03 0:40 ` David Woodhouse
2016-02-03 8:13 ` Oded Gabbay
2016-02-03 8:40 ` David Woodhouse
2016-02-03 9:21 ` Oded Gabbay
2016-02-03 10:15 ` David Woodhouse
2016-02-03 11:01 ` Oded Gabbay
2016-02-03 11:07 ` Oded Gabbay
2016-02-03 11:35 ` David Woodhouse
2016-02-03 11:41 ` David Woodhouse
2016-02-03 11:41 ` Oded Gabbay
2016-02-03 12:22 ` David Woodhouse
2016-02-25 13:49 ` Joerg Roedel
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=20160129095028.GA10767@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=j.glisse@gmail.com \
--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).