From: Jason Gunthorpe <jgg@ziepe.ca>
To: David Rientjes <rientjes@google.com>
Cc: Wei Xu <weixugc@google.com>,
lsf-pc@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>,
Dan Williams <dan.j.williams@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Greg Thelen <gthelen@google.com>, Paul Turner <pjt@google.com>,
Shakeel Butt <shakeelb@google.com>
Subject: Re: [LSF/MM/BPF TOPIC] Userspace managed memory tiering
Date: Sat, 19 Jun 2021 20:43:03 -0300 [thread overview]
Message-ID: <20210619234303.GC1096940@ziepe.ca> (raw)
In-Reply-To: <f38733a7-d623-5f0-6941-f84193c49e42@google.com>
On Fri, Jun 18, 2021 at 02:07:08PM -0700, David Rientjes wrote:
> On Fri, 18 Jun 2021, Wei Xu wrote:
>
> > In this proposal, I'd like to discuss userspace-managed memory tiering
> > and the kernel support that it needs.
> >
>
> Thanks Wei. Yes, this would be very useful to discuss at LSFMMBPF.
>
> It would also be very helpful to hear from other interested parties here
> on the mailing list ahead of time. It would be great to know the
> motivations and priorities of others interested in memory tiering for the
> use cases that Wei enumerated so that we can do some early brainstorming.
This reminds me quite alot of the pitch that was given for the hmm
migration user space policy stuff aimed at GPUs, but perhaps
differently generalized?
Jason
next prev parent reply other threads:[~2021-06-19 23:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 17:50 [LSF/MM/BPF TOPIC] Userspace managed memory tiering Wei Xu
2021-06-18 19:13 ` Zi Yan
2021-06-18 19:23 ` Wei Xu
2021-06-18 21:07 ` David Rientjes
2021-06-19 23:43 ` Jason Gunthorpe [this message]
2021-06-21 18:58 ` Yang Shi
2021-06-22 3:00 ` Huang, Ying
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=20210619234303.GC1096940@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=gthelen@google.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=pjt@google.com \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=tim.c.chen@linux.intel.com \
--cc=weixugc@google.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).