From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Jerome Glisse <j.glisse@gmail.com>,
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: Mon, 01 Feb 2016 21:16:02 +0530 [thread overview]
Message-ID: <87bn805t8l.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160128175536.GA20797@gmail.com>
Jerome Glisse <j.glisse@gmail.com> writes:
> 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).
>
> I want to discuss how to move forward with HMM merging and i
> hope that by MM summit time i will be able to share more
> informations publicly on devices which rely on HMM.
>
I mentioned in my request to attend mail, I would like to attend this
discussion. I am wondering whether we can split the series further to
mmu_notifier bits and then the page table mirroring bits. Can the mmu notifier
changes go in early so that we can merge the page table mirroring later ?
Can be page table mirroring bits be built as a kernel module ?
-aneesh
--
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-02-01 15:46 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
2016-01-29 13:35 ` Jerome Glisse
2016-02-01 15:46 ` Aneesh Kumar K.V [this message]
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=87bn805t8l.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--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).