Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3;
MIME-Version: 1.0
References: <ZV5zGROLefrsEcHJ@r13-u19.micron.com> <20231122133944.297ce0001fb51214096dfb6c@linux-foundation.org>
In-Reply-To: <20231122133944.297ce0001fb51214096dfb6c@linux-foundation.org>
From:   Vinicius Petrucci <vpetrucci@gmail.com>
Date:   Wed, 22 Nov 2023 17:57:00 -0600
Message-ID: <CAEZ6=UPDPyJ=gq7U50scPM7CUSc8mutJoTodeN6fPdd1YzzxVA@mail.gmail.com>
Subject: Re: [RFC PATCH] mm/mbind: Introduce process_mbind() syscall for
 external memory binding
To:     Andrew Morton <akpm@linux-foundation.org>
Cc:     linux-mm@vger.kernel.org, linux-cxl@vger.kernel.org,
        linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
        linux-api@vger.kernel.org, minchan@kernel.org,
        dave.hansen@linux.intel.com, x86@kernel.org,
        Jonathan.Cameron@huawei.com, aneesh.kumar@linux.ibm.com,
        ying.huang@intel.com, dan.j.williams@intel.com,
        hezhongkun.hzk@bytedance.com, fvdl@google.com, surenb@google.com,
        rientjes@google.com, hannes@cmpxchg.org, mhocko@suse.com,
        Hasan.Maruf@amd.com, jgroves@micron.com, ravis.opensrc@micron.com,
        sthanneeru@micron.com, emirakhur@micron.com,
        vtavarespetr@micron.com, Gregory Price <gregory.price@memverge.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Wed, Nov 22, 2023 at 3:39=E2=80=AFPM Andrew Morton <akpm@linux-foundatio=
n.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.c=
om
>

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/#m950f26=
bdd6ce494b20ba170cc1f6db85e1924e8e

I would appreciate it if others could kindly evaluate what appears to
be the suitable course of action moving forward.

Thank you!