linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lstoakes@gmail.com>
To: Frank van der Linden <fvdl@google.com>
Cc: linux-mm@kvack.org
Subject: Re: [LSF/MM/BPF TOPIC] userspace control of memory management
Date: Fri, 28 Apr 2023 16:00:15 +0100	[thread overview]
Message-ID: <4cefb151-df30-40f3-b45b-e7ca3f362bf2@lucifer.local> (raw)
In-Reply-To: <CAPTztWYAiroY3E8pwB+rnPGA1K9HLhkpQp1Gy9C1dEuS1FhWGg@mail.gmail.com>

On Tue, Feb 28, 2023 at 04:15:21PM -0800, Frank van der Linden wrote:
> I propose this discussion topic for LSF/MM/BPF.
>
> In a world where memory topologies are becoming more complicated, is
> it still possible to have an approach where the kernel deals with
> memory management to everyone's satisfaction?
>
> The answer seemingly has been "not quite", since madvise and mempolicy
> exist. With things like cxl.mem coming into existence, a heterogeneous
> memory setup will become more common.
>
> The number of madvise options keeps growing. There is now a
> process_madvise, and there are proposed extensions for the mempolicy
> systemcalls, allowing one process to control the policy of another, as
> well. There are exported cgroup interfaces to control reclaim, and
> discussions have taken place on explicit control reclaim-as-demotion
> to other nodes.
>
> Is this the right approach? If so, would it be a good idea to
> optionally provide BPF hooks to control certain behavior, and let
> userspace direct things even more? Is that even possible,
> performance-wise? Would it make sense to be able to influence the
> MGLRU generation process in a more direct way if needed?
>
> I think a discussion about these points would be interesting. Or, I
> should say, further discussion.
>
> What do you think?
>
> Thanks,
>
> - Frank
>

Surely userfaultfd is part of this equation too? I definitely think this is a
useful converastion to have, in any case!


      parent reply	other threads:[~2023-04-28 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  0:15 Frank van der Linden
2023-03-02  3:10 ` David Rientjes
     [not found] ` <CAPTztWY49XP-7GDHuvV2fNDCeJzd0vAac6n+rJ9KfWr6cyZ5ww@mail.gmail.com>
2023-04-28 14:18   ` [Lsf-pc] Fwd: " Michal Hocko
2023-04-28 14:54     ` Matthew Wilcox
2023-04-28 17:47       ` Michal Hocko
2023-05-04 18:47     ` Hao Luo
2023-04-28 15:00 ` Lorenzo Stoakes [this message]

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=4cefb151-df30-40f3-b45b-e7ca3f362bf2@lucifer.local \
    --to=lstoakes@gmail.com \
    --cc=fvdl@google.com \
    --cc=linux-mm@kvack.org \
    /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