From: Felix Kuehling <felix.kuehling@amd.com>
To: Linux MM <linux-mm@kvack.org>,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
Jason Gunthorpe <jgg@mellanox.com>,
Jerome Glisse <jglisse@redhat.com>,
Ralph Campbell <rcampbell@nvidia.com>,
Theodore Ts'o <tytso@mit.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@techsingularity.net>,
Peter Zijlstra <peterz@infradead.org>,
"Phillips, Daniel" <Daniel.Phillips@amd.com>,
"Sierra Guiza, Alejandro (Alex)" <Alex.Sierra@amd.com>
Subject: BoF at LPC: Documenting the Heterogeneous Memory Model Architecture
Date: Tue, 21 Sep 2021 15:19:02 -0400 [thread overview]
Message-ID: <23aeacb6-0cd9-d10f-76bc-3c9d33905daa@amd.com> (raw)
As the programming models for GPU-based high-performance computing
applications are evolving, HMM is helping us integrate the GPU memory
management more closely with the kernel's virtual memory management. As
a result we can provide a shared virtual address space with
demand-paging and page-based migrations of anonymous pages to/from
device memory. A patch series by AMD [1, 2] to add support for
cache-coherent, CPU-accessible device memory has brought up some fairly
fundamental questions about HMM and its interaction with virtual memory
management, page cache and file systems. We'd like to use the chance of
getting together for a BoF [3] at LPC to raise awareness for HMM outside
the GPU driver code, identify gaps in the architectural documentation
and clarify our priorities for future development.
Thank you, Daniel, for suggesting the BoF and getting it scheduled. It's
set for Friday, 10am Pacific, 1pm Eastern, 5pm UTC.
I am registered at LPC. Daniel got a speaker's pass. We're still trying
to work something out for Alex.
I hope to see many of you on Friday.
Best regards,
Felix
[1] https://patchwork.freedesktop.org/series/94611/
[2] https://patchwork.freedesktop.org/series/90706/
[3] https://linuxplumbersconf.org/event/11/contributions/1123/
--
F e l i x K u e h l i n g
PMTS Software Development Engineer | Linux Compute Kernel
1 Commerce Valley Dr. East, Markham, ON L3T 7X6 Canada
(O) +1(289)695-1597
_ _ _ _____ _____
/ \ | \ / | | _ \ \ _ |
/ A \ | \M/ | | |D) ) /|_| |
/_/ \_\ |_| |_| |_____/ |__/ \| facebook.com/AMD | amd.com
next reply other threads:[~2021-09-21 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 19:19 Felix Kuehling [this message]
2021-09-23 20:25 ` BoF at LPC: Documenting the Heterogeneous Memory Model Architecture Felix Kuehling
2021-09-23 20:39 ` Matthew Wilcox
2021-09-23 21:40 ` Phillips, Daniel
2021-09-23 23:00 ` Daniel Stone
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=23aeacb6-0cd9-d10f-76bc-3c9d33905daa@amd.com \
--to=felix.kuehling@amd.com \
--cc=Alex.Sierra@amd.com \
--cc=Daniel.Phillips@amd.com \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=jgg@mellanox.com \
--cc=jglisse@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=peterz@infradead.org \
--cc=rcampbell@nvidia.com \
--cc=tytso@mit.edu \
/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).