From: David Hildenbrand <david@redhat.com>
To: zhuweixi <weixi.zhu@huawei.com>,
"Dave Airlie" <airlied@gmail.com>,
"Christian König" <christian.koenig@amd.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"weixi.zhu@openeuler.sh" <weixi.zhu@openeuler.sh>,
"mgorman@suse.de" <mgorman@suse.de>,
"jglisse@redhat.com" <jglisse@redhat.com>,
"rcampbell@nvidia.com" <rcampbell@nvidia.com>,
"jhubbard@nvidia.com" <jhubbard@nvidia.com>,
"apopple@nvidia.com" <apopple@nvidia.com>,
"mhairgrove@nvidia.com" <mhairgrove@nvidia.com>,
"ziy@nvidia.com" <ziy@nvidia.com>,
"alexander.deucher@amd.com" <alexander.deucher@amd.com>,
"Xinhui.Pan@amd.com" <Xinhui.Pan@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Felix.Kuehling@amd.com" <Felix.Kuehling@amd.com>,
"ogabbay@kernel.org" <ogabbay@kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"leonro@nvidia.com" <leonro@nvidia.com>,
"zhenyuw@linux.intel.com" <zhenyuw@linux.intel.com>,
"zhi.a.wang@intel.com" <zhi.a.wang@intel.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"joonas.lahtinen@linux.intel.com"
<joonas.lahtinen@linux.intel.com>,
"rodrigo.vivi@intel.com" <rodrigo.vivi@intel.com>,
"tvrtko.ursulin@linux.intel.com" <tvrtko.ursulin@linux.intel.com>,
"Zeng, Oak" <oak.zeng@intel.com>
Subject: Re: [RFC PATCH 0/6] Supporting GMEM (generalized memory management) for external memory devices
Date: Fri, 1 Dec 2023 10:29:34 +0100 [thread overview]
Message-ID: <135306b4-2f94-4266-8f72-90315bb846b4@redhat.com> (raw)
In-Reply-To: <f4ec70345800432caa94d662f49370f6@huawei.com>
On 01.12.23 03:44, zhuweixi wrote:
> Thanks!
I hope you understood that that was a joke :)
> I am planning to present GMEM in Linux MM Alignment Sessions so I can collect more input from the mm developers.
Sounds good. But please try inviting key HMM/driver developer as well.
Most of the core-mm folks attending that meeting are not that familiar
with these concepts and they are usually not happy about:
(1) More core-MM complexity for things that can be neatly handled in
separate subsystems with the existing infrastructure already.
(2) One new way of doing things why the other things remain in place.
(3) New MMAP flags. Usually you have a hard time getting this in.
Sometimes, there are other ways (e.g., special-purpose file-
systems).
(4) Changing controversial core-mm design decisions to handle corner
cases.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-12-01 9:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:50 Weixi Zhu
2023-11-28 12:50 ` [RFC PATCH 1/6] mm/gmem: add heterogeneous NUMA node Weixi Zhu
2023-11-28 12:50 ` [RFC PATCH 2/6] mm/gmem: add arch-independent abstraction to track address mapping status Weixi Zhu
2023-11-29 8:33 ` emily
2023-11-29 8:49 ` zhuweixi
2023-12-01 9:23 ` David Hildenbrand
2023-12-02 14:50 ` Pedro Falcato
2023-12-04 10:21 ` David Hildenbrand
2023-11-28 12:50 ` [RFC PATCH 3/6] mm/gmem: add GMEM (Generalized Memory Management) interface for external accelerators Weixi Zhu
2023-11-28 12:50 ` [RFC PATCH 4/6] mm/gmem: add new syscall hmadvise() to issue memory hints for heterogeneous NUMA nodes Weixi Zhu
2023-11-28 12:50 ` [RFC PATCH 5/6] mm/gmem: resolve VMA conflicts for attached peer devices Weixi Zhu
2023-11-28 12:50 ` [RFC PATCH 6/6] mm/gmem: extending Linux core MM to support unified virtual address space Weixi Zhu
2023-11-28 13:06 ` [RFC PATCH 0/6] Supporting GMEM (generalized memory management) for external memory devices Christian König
2023-11-29 5:14 ` Dave Airlie
2023-11-29 8:27 ` zhuweixi
2023-11-29 15:22 ` Christian König
2023-11-30 7:22 ` zhuweixi
2023-11-30 13:05 ` Christian König
2023-12-01 2:37 ` zhuweixi
2023-12-01 21:28 ` Philipp Stanner
2023-11-30 14:55 ` David Hildenbrand
2023-12-01 2:44 ` zhuweixi
2023-12-01 9:29 ` David Hildenbrand [this message]
2023-11-28 13:09 ` Christian König
2023-11-29 22:23 ` Zeng, Oak
2023-11-30 8:27 ` Christian König
2023-11-30 10:48 ` zhuweixi
2023-12-01 5:48 ` Zeng, Oak
2023-12-01 6:11 ` Alistair Popple
2023-12-01 13:16 ` Christian König
2023-12-03 23:32 ` Alistair Popple
2023-12-04 9:35 ` Christian König
2023-12-01 6:01 ` Alistair Popple
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=135306b4-2f94-4266-8f72-90315bb846b4@redhat.com \
--to=david@redhat.com \
--cc=Felix.Kuehling@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=apopple@nvidia.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jgg@nvidia.com \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhairgrove@nvidia.com \
--cc=oak.zeng@intel.com \
--cc=ogabbay@kernel.org \
--cc=rcampbell@nvidia.com \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=weixi.zhu@huawei.com \
--cc=weixi.zhu@openeuler.sh \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.com \
--cc=ziy@nvidia.com \
/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