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: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"leonro@nvidia.com" <leonro@nvidia.com>,
"apopple@nvidia.com" <apopple@nvidia.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"mgorman@suse.de" <mgorman@suse.de>,
"ziy@nvidia.com" <ziy@nvidia.com>,
"zhi.a.wang@intel.com" <zhi.a.wang@intel.com>,
"rcampbell@nvidia.com" <rcampbell@nvidia.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"weixi.zhu@openeuler.sh" <weixi.zhu@openeuler.sh>,
"jhubbard@nvidia.com" <jhubbard@nvidia.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"mhairgrove@nvidia.com" <mhairgrove@nvidia.com>,
"jglisse@redhat.com" <jglisse@redhat.com>,
"rodrigo.vivi@intel.com" <rodrigo.vivi@intel.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"tvrtko.ursulin@linux.intel.com" <tvrtko.ursulin@linux.intel.com>,
"Felix.Kuehling@amd.com" <Felix.Kuehling@amd.com>,
"Xinhui.Pan@amd.com" <Xinhui.Pan@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alexander.deucher@amd.com" <alexander.deucher@amd.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"ogabbay@kernel.org" <ogabbay@kernel.org>
Subject: Re: [RFC PATCH 0/6] Supporting GMEM (generalized memory management) for external memory devices
Date: Thu, 30 Nov 2023 15:55:28 +0100 [thread overview]
Message-ID: <188814aa-4f55-40c6-961c-6105c89d76f3@redhat.com> (raw)
In-Reply-To: <a07fd33c6f9e44418c528de06f89707e@huawei.com>
On 29.11.23 09:27, zhuweixi wrote:
> Glad to hear that more sharable code is desirable.
> IMHO, for a common MM subsystem, it is more beneficial for
> GMEM to extend core MM instead of building a separate one.
More core-mm complexity, awesome, we all love that! ;)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-11-30 14:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:50 [RFC PATCH 0/6] Supporting GMEM (generalized memory management) for external memory devices 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:25 ` linear cannon
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 [this message]
2023-12-01 2:44 ` zhuweixi
2023-12-01 9:29 ` David Hildenbrand
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=188814aa-4f55-40c6-961c-6105c89d76f3@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=jgg@nvidia.com \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.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=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=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;
as well as URLs for NNTP newsgroup(s).