linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Muyang Tian <tianmuyang@huawei.com>
To: <yuanchu@google.com>
Cc: <Michael@michaellarabel.com>, <akpm@linux-foundation.org>,
	<bpf@vger.kernel.org>, <corbet@lwn.net>,
	<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
	<liuxin350@huawei.com>, <liwei883@huawei.com>,
	<tianmuyang@huawei.com>, <wuchangye@huawei.com>,
	<xiesongyang@huawei.com>, <yanan@huawei.com>, <yuzhao@google.com>,
	<zhangmingyi5@huawei.com>
Subject: Re: [RFC PATCH 0/2] mm: multi-gen LRU: per-process heatmaps
Date: Thu, 9 Jan 2025 19:48:47 +0800	[thread overview]
Message-ID: <20250109114847.539237-1-tianmuyang@huawei.com> (raw)
In-Reply-To: <CAJj2-QEtASHEfiYuoKrfx7n1UjDS1e+aF0LdYB5vhBUUS3cq8g@mail.gmail.com>

Hi Yuanchu,

I'm working on observability and the programmable page generation policy of MGLRU based on eBPF, using a similar approach to yours. 
I'd like to know if there is any related work, such as the application of eBPF in MGLRU? 
Also, this RFC provides a user space interface to call run_aging(), which is called periodically in the demo. 
Do you plan to optimize this, perhaps by calling run_aging() based on page access observation results?

Thanks!



  reply	other threads:[~2025-01-09 11:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11  8:34 Yuanchu Xie
2022-09-11  8:34 ` [RFC PATCH 1/2] mm: multi-gen LRU: support page access info harvesting with eBPF Yuanchu Xie
2022-09-11  8:34 ` [RFC PATCH 2/2] mm: add a BPF-based per-process heatmap tool Yuanchu Xie
2025-01-03  3:15 ` [RFC PATCH 0/2] mm: multi-gen LRU: per-process heatmaps Muyang Tian
2025-01-06 20:19   ` Yuanchu Xie
2025-01-09 11:48     ` Muyang Tian [this message]
2025-01-30  1:42       ` Yuanchu Xie

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=20250109114847.539237-1-tianmuyang@huawei.com \
    --to=tianmuyang@huawei.com \
    --cc=Michael@michaellarabel.com \
    --cc=akpm@linux-foundation.org \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuxin350@huawei.com \
    --cc=liwei883@huawei.com \
    --cc=wuchangye@huawei.com \
    --cc=xiesongyang@huawei.com \
    --cc=yanan@huawei.com \
    --cc=yuanchu@google.com \
    --cc=yuzhao@google.com \
    --cc=zhangmingyi5@huawei.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