From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: damon@lists.linux.dev, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: DAMON Release Newsletter for v7.2-rc1
Date: Sun, 28 Jun 2026 14:42:08 -0700 [thread overview]
Message-ID: <20260628214208.94619-1-sj@kernel.org> (raw)
In-Reply-To: <20260628211904.94361-1-sj@kernel.org>
On Sun, 28 Jun 2026 14:19:03 -0700 SJ Park <sj@kernel.org> wrote:
> Hello community,
>
>
> This newsletter covers DAMON features that landed on the mainline, queued for
> the mainline, development statistics and misc events that were interesting to
> me that happened in v7.1-rc1..v7.2-rc1 time period (2026-04-26..2026-06-28).
>
> The newsletter covering the previous release cycle (v7.0-rc1..v7.1-rc1) is
> also available [1].
>
> TLDR
> ====
>
> The last development cycle for DAMON was the busiest cycle of its mainline
> history (~6 years, since 2021 September). 12 Authors landed 106 DAMON patches
s/6 years/5 years/
Sorry, I'm definitely not good at counting. Sometimes even worse than LLM.
> for a number of changes including 7 new features on the mainline. A roadmap
> for extending DAMON to utilize AMD IBS, Intel PEBS like h/w features and do
> per-CPUs/threads/reads/writes monitoring is made.
[...]
> The 6.17 development cycle was the busiest DAMON development cycle in history
> (~6 years since 5.15). This cycle broke the record.
s/6 years/5 years/
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-06-28 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 21:19 DAMON Release Newsletter for v7.2-rc1 SJ Park
2026-06-28 21:42 ` SJ 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=20260628214208.94619-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--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