From: Gregory Price <gregory.price@memverge.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vinicius Petrucci <vpetrucci@gmail.com>,
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
Subject: Re: [RFC PATCH] mm/mbind: Introduce process_mbind() syscall for external memory binding
Date: Wed, 22 Nov 2023 16:45:08 -0500 [thread overview]
Message-ID: <ZV52ZD7AbIBoYs2t@memverge.com> (raw)
In-Reply-To: <20231122133944.297ce0001fb51214096dfb6c@linux-foundation.org>
On Wed, Nov 22, 2023 at 01:39:44PM -0800, Andrew Morton wrote:
> On Wed, 22 Nov 2023 15:31:05 -0600 Vinicius Petrucci <vpetrucci@gmail.com> wrote:
>
> > From: Vinicius Tavares Petrucci <vtavarespetr@micron.com>
> >
> > This patch introduces `process_mbind()` to enable a userspace orchestrator with
> > an understanding of another process's memory layout to alter its memory policy.
>
>
> 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
>
> Please share notes ;)
Heh, we discussed doing this at linux plumbers, as well as a long set of
RFC's related to weighted mempolicies.
Guess we were in a bit of a race to RFC without knowing!
more context: mhocko suggested this interface would be welcome and useful
before the introduction of weighted inteleave.
link: https://lore.kernel.org/linux-mm/ZVNBMW8iJIGDyp0y@tiehlicka/
~Gregory
next prev parent reply other threads:[~2023-11-22 21:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 21:31 [RFC PATCH] mm/mbind: Introduce process_mbind() syscall for external memory binding Vinicius Petrucci
2023-11-22 21:39 ` Andrew Morton
2023-11-22 21:45 ` Gregory Price [this message]
2023-11-22 23:57 ` Vinicius Petrucci
2023-11-22 23:53 ` Gregory Price
2023-11-23 15:21 ` Vinicius Petrucci
2023-11-24 8:13 ` Zhongkun He
2023-11-23 21:42 ` Gregory Price
2023-11-30 9:34 ` Zhongkun He
2023-11-30 16:07 ` Gregory Price
2023-12-01 13:53 ` Zhongkun He
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=ZV52ZD7AbIBoYs2t@memverge.com \
--to=gregory.price@memverge.com \
--cc=Hasan.Maruf@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=emirakhur@micron.com \
--cc=fvdl@google.com \
--cc=hannes@cmpxchg.org \
--cc=hezhongkun.hzk@bytedance.com \
--cc=jgroves@micron.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=ravis.opensrc@micron.com \
--cc=rientjes@google.com \
--cc=sthanneeru@micron.com \
--cc=surenb@google.com \
--cc=vpetrucci@gmail.com \
--cc=vtavarespetr@micron.com \
--cc=x86@kernel.org \
--cc=ying.huang@intel.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