linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Michal Hocko <mhocko@suse.com>
Cc: Frank van der Linden <fvdl@google.com>,
	lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Lsf-pc] Fwd: [LSF/MM/BPF TOPIC] userspace control of memory management
Date: Fri, 28 Apr 2023 15:54:31 +0100	[thread overview]
Message-ID: <ZEveJ3OmysVDVZ8m@casper.infradead.org> (raw)
In-Reply-To: <ZEvVqMtnU142GMEU@dhcp22.suse.cz>

On Fri, Apr 28, 2023 at 04:18:16PM +0200, Michal Hocko wrote:
> For some reason I cannot find this email in my linux-mm inbox and I
> cannot find it in any archives so let me add linux-mm and lkml again for
> future reference.

Hm, I found it by searching for 'lsf' on lore.kernel.org in the linux-mm
archive.

https://lore.kernel.org/linux-mm/CAPTztWYAiroY3E8pwB+rnPGA1K9HLhkpQp1Gy9C1dEuS1FhWGg@mail.gmail.com/

Here are the other topics I found:

Eliminate vmap/vmalloc lock contention
Reducing direct map fragmentation
Stable process
Phyrs discussion
Live migration over CXL
SMDK MM changes for CXL
Sunsetting buffer_heads
HGM for hugetlbfs
Reducing zombie memcgs
Swap abstraction / native zswap
SLOB/SLAB allocator removal + future SLUB improvements
Session for CXL memory
Memory profiling using code tagging
Cloud storage optimizations
Flexible orders for anonymous folios
VM Memory Overcommit
State of The Page
Userspace control of memory management
IOMAP conversion status update
DAMON Updates and Future Plans
Make BPF memory allocator more robust
Virtual Machine Memory Passthrough
Scalable Pagefaults
Single Owner Memory
CXL Fabric Manager Architecture
Using hardware counters to determine hot/cold pages
Sframe: An orc like stack unwinder
Mm docs
Tracing mapped pages for quicker boot performance

(not all of these are the exact titles used by the authors)


  reply	other threads:[~2023-04-28 14:54 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 [this message]
2023-04-28 17:47       ` Michal Hocko
2023-05-04 18:47     ` Hao Luo
2023-04-28 15:00 ` Lorenzo Stoakes

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=ZEveJ3OmysVDVZ8m@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=fvdl@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=mhocko@suse.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