[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <135306b4-2f94-4266-8f72-90315bb846b4@redhat.com>
Date: Fri, 1 Dec 2023 10:29:34 +0100
From: David Hildenbrand <david@...hat.com>
To: zhuweixi <weixi.zhu@...wei.com>, Dave Airlie <airlied@...il.com>,
Christian König <christian.koenig@....com>
Cc: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"weixi.zhu@...neuler.sh" <weixi.zhu@...neuler.sh>,
"mgorman@...e.de" <mgorman@...e.de>,
"jglisse@...hat.com" <jglisse@...hat.com>,
"rcampbell@...dia.com" <rcampbell@...dia.com>,
"jhubbard@...dia.com" <jhubbard@...dia.com>,
"apopple@...dia.com" <apopple@...dia.com>,
"mhairgrove@...dia.com" <mhairgrove@...dia.com>,
"ziy@...dia.com" <ziy@...dia.com>,
"alexander.deucher@....com" <alexander.deucher@....com>,
"Xinhui.Pan@....com" <Xinhui.Pan@....com>,
"amd-gfx@...ts.freedesktop.org" <amd-gfx@...ts.freedesktop.org>,
"Felix.Kuehling@....com" <Felix.Kuehling@....com>,
"ogabbay@...nel.org" <ogabbay@...nel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"jgg@...dia.com" <jgg@...dia.com>,
"leonro@...dia.com" <leonro@...dia.com>,
"zhenyuw@...ux.intel.com" <zhenyuw@...ux.intel.com>,
"zhi.a.wang@...el.com" <zhi.a.wang@...el.com>,
"intel-gvt-dev@...ts.freedesktop.org"
<intel-gvt-dev@...ts.freedesktop.org>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"jani.nikula@...ux.intel.com" <jani.nikula@...ux.intel.com>,
"joonas.lahtinen@...ux.intel.com" <joonas.lahtinen@...ux.intel.com>,
"rodrigo.vivi@...el.com" <rodrigo.vivi@...el.com>,
"tvrtko.ursulin@...ux.intel.com" <tvrtko.ursulin@...ux.intel.com>,
"Zeng, Oak" <oak.zeng@...el.com>
Subject: Re: [RFC PATCH 0/6] Supporting GMEM (generalized memory management)
for external memory devices
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
Powered by blists - more mailing lists