[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aJAfTUh-49pYuhbg@3c06303d853a>
Date: Sun, 3 Aug 2025 19:47:41 -0700
From: Andrew Paniakin <apanyaki@...zon.com>
To: SeongJae Park <sj@...nel.org>
CC: "Liam R. Howlett" <Liam.Howlett@...cle.com>, Andrew Morton
<akpm@...ux-foundation.org>, David Hildenbrand <david@...hat.com>, Jann Horn
<jannh@...gle.com>, Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, "Michal
Hocko" <mhocko@...e.com>, Mike Rapoport <rppt@...nel.org>, Pedro Falcato
<pfalcato@...e.de>, Suren Baghdasaryan <surenb@...gle.com>, Vlastimil Babka
<vbabka@...e.cz>, <damon@...ts.linux.dev>, <kernel-team@...a.com>,
<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
<amazon-linux-kernel@...zon.com>
Subject: Re: [RFC v2 0/7] mm/damon: extend for page faults reporting based
access monitoring
On 27/07/2025, SeongJae Park wrote:
> TL; DR: Extend DAMON interface between core and operation sets for
> operation set driven report-based monitoring such as per-CPU and
> write-only access monitoring. Further introduce an example physical
> address space monitoring operation set that uses page faults as the
> source of the information.
Thank you very much for starting this update. RFC mentions write-only
monitoring, this feature particularly would be really helpful in some of
our use cases such as lightweight live migration target selection, so we
are looking forward to collaborate in development and testing activity!
Powered by blists - more mailing lists