[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEZ6=UPDPyJ=gq7U50scPM7CUSc8mutJoTodeN6fPdd1YzzxVA@mail.gmail.com>
Date: Wed, 22 Nov 2023 17:57:00 -0600
From: Vinicius Petrucci <vpetrucci@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-mm@...r.kernel.org, linux-cxl@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
linux-api@...r.kernel.org, minchan@...nel.org,
dave.hansen@...ux.intel.com, x86@...nel.org,
Jonathan.Cameron@...wei.com, aneesh.kumar@...ux.ibm.com,
ying.huang@...el.com, dan.j.williams@...el.com,
hezhongkun.hzk@...edance.com, fvdl@...gle.com, surenb@...gle.com,
rientjes@...gle.com, hannes@...xchg.org, mhocko@...e.com,
Hasan.Maruf@....com, jgroves@...ron.com, ravis.opensrc@...ron.com,
sthanneeru@...ron.com, emirakhur@...ron.com,
vtavarespetr@...ron.com, Gregory Price <gregory.price@...verge.com>
Subject: Re: [RFC PATCH] mm/mbind: Introduce process_mbind() syscall for
external memory binding
On Wed, Nov 22, 2023 at 3:39 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
> I'm having deja vu. Not 10 minutes ago, Gregory sent out a patchset
> which does the same thing.
>
> https://lkml.kernel.org/r/20231122211200.31620-1-gregory.price@memverge.com
>
Certainly, it appears that we were addressing the same matter but
approaching it from different perspectives or discussions.
And we hastened to submit our RFCs before the Thanksgiving break. :-)
The patch I sent originated from the thread, and the subsequent
discussion commenced with the 'pidfd_set_mempolicy' RFC, possibly
influenced by the 'process_madvise.'
Specifically, the concept of a 'process_mbind()' syscall was suggested
by Frank van der Linden (Google):
https://lkml.kernel.org/linux-mm/Y0WEbCqJHjnqsg8n@dhcp22.suse.cz/T/#m950f26bdd6ce494b20ba170cc1f6db85e1924e8e
I would appreciate it if others could kindly evaluate what appears to
be the suitable course of action moving forward.
Thank you!
Powered by blists - more mailing lists