From: SeongJae Park <sjpark@amazon.com>
To: SeongJae Park <sjpark@amazon.com>
Cc: <akpm@linux-foundation.org>, <Jonathan.Cameron@Huawei.com>,
<aarcange@redhat.com>, <acme@kernel.org>,
<alexander.shishkin@linux.intel.com>, <amit@kernel.org>,
<benh@kernel.crashing.org>, <brendan.d.gregg@gmail.com>,
<brendanhiggins@google.com>, <cai@lca.pw>,
<colin.king@canonical.com>, <corbet@lwn.net>, <david@redhat.com>,
<dwmw@amazon.com>, <elver@google.com>, <fan.du@intel.com>,
<foersleo@amazon.de>, <gthelen@google.com>, <irogers@google.com>,
<jolsa@redhat.com>, <kirill@shutemov.name>,
<mark.rutland@arm.com>, <mgorman@suse.de>, <minchan@kernel.org>,
<mingo@redhat.com>, <namhyung@kernel.org>, <peterz@infradead.org>,
<rdunlap@infradead.org>, <riel@surriel.com>,
<rientjes@google.com>, <rostedt@goodmis.org>, <rppt@kernel.org>,
<sblbir@amazon.com>, <shakeelb@google.com>, <shuah@kernel.org>,
<sj38.park@gmail.com>, <snu@amazon.de>, <vbabka@suse.cz>,
<vdavydov.dev@gmail.com>, <yang.shi@linux.alibaba.com>,
<ying.huang@intel.com>, <zgf574564920@gmail.com>,
<linux-damon@amazon.com>, <linux-mm@kvack.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<greg@kroah.com>
Subject: Re: [PATCH v24 00/14] Subject: Introduce Data Access MONitor (DAMON)
Date: Thu, 4 Mar 2021 11:07:32 +0100 [thread overview]
Message-ID: <20210304100732.7844-1-sjpark@amazon.com> (raw)
In-Reply-To: <20210204153150.15948-1-sjpark@amazon.com>
On Thu, 4 Feb 2021 16:31:36 +0100 SeongJae Park <sjpark@amazon.com> wrote:
> From: SeongJae Park <sjpark@amazon.de>
[...]
>
> Introduction
> ============
>
> DAMON is a data access monitoring framework for the Linux kernel. The core
> mechanisms of DAMON called 'region based sampling' and 'adaptive regions
> adjustment' (refer to 'mechanisms.rst' in the 11th patch of this patchset for
> the detail) make it
>
> - accurate (The monitored information is useful for DRAM level memory
> management. It might not appropriate for Cache-level accuracy, though.),
> - light-weight (The monitoring overhead is low enough to be applied online
> while making no impact on the performance of the target workloads.), and
> - scalable (the upper-bound of the instrumentation overhead is controllable
> regardless of the size of target workloads.).
>
> Using this framework, therefore, several memory management mechanisms such as
> reclamation and THP can be optimized to aware real data access patterns.
> Experimental access pattern aware memory management optimization works that
> incurring high instrumentation overhead will be able to have another try.
>
> Though DAMON is for kernel subsystems, it can be easily exposed to the user
> space by writing a DAMON-wrapper kernel subsystem. Then, user space users who
> have some special workloads will be able to write personalized tools or
> applications for deeper understanding and specialized optimizations of their
> systems.
>
[...]
>
> Baseline and Complete Git Trees
> ===============================
>
> The patches are based on the v5.10. You can also clone the complete git
> tree:
>
> $ git clone git://github.com/sjp38/linux -b damon/patches/v24
>
> The web is also available:
> https://github.com/sjp38/linux/releases/tag/damon/patches/v24
>
> There are a couple of trees for entire DAMON patchset series. It includes
> future features. The first one[1] contains the changes for latest release,
> while the other one[2] contains the changes for next release.
>
> [1] https://github.com/sjp38/linux/tree/damon/master
> [2] https://github.com/sjp38/linux/tree/damon/next
For people who prefer LTS kernels, I decided to maintain two more trees that
repectively based on latest two LTS kernels and contains backports of the
latest 'damon/master' tree, as below. Please use those if you want to test
DAMON but using LTS.
- For v5.4.y: https://github.com/sjp38/linux/tree/damon/for-v5.4.y
- For v5.10.y: https://github.com/sjp38/linux/tree/damon/for-v5.10.y
Thanks,
SeongJae Park
prev parent reply other threads:[~2021-03-04 10:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 15:31 [PATCH v24 00/14] Subject: Introduce Data Access MONitor (DAMON) SeongJae Park
2021-02-04 15:31 ` [PATCH v24 01/14] mm: " SeongJae Park
2021-02-04 15:31 ` [PATCH v24 02/14] mm/damon/core: Implement region-based sampling SeongJae Park
2021-02-04 15:31 ` [PATCH v24 03/14] mm/damon: Adaptively adjust regions SeongJae Park
2021-02-04 15:31 ` [PATCH v24 04/14] mm/idle_page_tracking: Make PG_idle reusable SeongJae Park
2021-02-04 15:31 ` [PATCH v24 05/14] mm/damon: Implement primitives for the virtual memory address spaces SeongJae Park
2021-02-04 15:31 ` [PATCH v24 06/14] mm/damon: Add a tracepoint SeongJae Park
2021-02-04 15:31 ` [PATCH v24 07/14] mm/damon: Implement a debugfs-based user space interface SeongJae Park
2021-02-05 15:29 ` Greg KH
2021-02-05 15:59 ` SeongJae Park
2021-02-04 15:31 ` [PATCH v24 08/14] mm/damon/dbgfs: Implement recording feature SeongJae Park
2021-02-04 15:31 ` [PATCH v24 09/14] mm/damon/dbgfs: Export kdamond pid to the user space SeongJae Park
2021-02-04 15:31 ` [PATCH v24 10/14] mm/damon/dbgfs: Support multiple contexts SeongJae Park
2021-02-04 15:31 ` [PATCH v24 11/14] Documentation: Add documents for DAMON SeongJae Park
2021-02-24 7:49 ` SeongJae Park
2021-02-04 15:31 ` [PATCH v24 12/14] mm/damon: Add kunit tests SeongJae Park
2021-02-04 15:31 ` [PATCH v24 13/14] mm/damon: Add user space selftests SeongJae Park
2021-02-04 15:31 ` [PATCH v24 14/14] MAINTAINERS: Update for DAMON SeongJae Park
2021-02-24 13:30 ` [PATCH v24 00/14] Subject: Introduce Data Access MONitor (DAMON) SeongJae Park
2021-03-04 10:07 ` SeongJae Park [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=20210304100732.7844-1-sjpark@amazon.com \
--to=sjpark@amazon.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=aarcange@redhat.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=amit@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=brendan.d.gregg@gmail.com \
--cc=brendanhiggins@google.com \
--cc=cai@lca.pw \
--cc=colin.king@canonical.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dwmw@amazon.com \
--cc=elver@google.com \
--cc=fan.du@intel.com \
--cc=foersleo@amazon.de \
--cc=greg@kroah.com \
--cc=gthelen@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kirill@shutemov.name \
--cc=linux-damon@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=sblbir@amazon.com \
--cc=shakeelb@google.com \
--cc=shuah@kernel.org \
--cc=sj38.park@gmail.com \
--cc=snu@amazon.de \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
--cc=yang.shi@linux.alibaba.com \
--cc=ying.huang@intel.com \
--cc=zgf574564920@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.