From:   Oleksandr Natalenko <oleksandr@natalenko.name>
To:     akpm@linux-foundation.org, SeongJae Park <sj@kernel.org>,
        Jonathan.Cameron@huawei.com
Cc:     amit@kernel.org, benh@kernel.crashing.org, corbet@lwn.net,
        david@redhat.com, dwmw@amazon.com, elver@google.com,
        foersleo@amazon.de, gthelen@google.com, markubo@amazon.de,
        rientjes@google.com, shakeelb@google.com, shuah@kernel.org,
        linux-damon@amazon.com, linux-mm@kvack.org,
        linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/15] Introduce DAMON-based Proactive Reclamation
Date:   Sun, 21 Nov 2021 23:32:12 +0100
Message-ID: <11868371.O9o76ZdvQC@natalenko.name>
In-Reply-To: <20211019150731.16699-1-sj@kernel.org>
References: <20211019150731.16699-1-sj@kernel.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hello.

On =C3=BAter=C3=BD 19. =C5=99=C3=ADjna 2021 17:07:16 CET SeongJae Park wrot=
e:
> In short, DAMON_RECLAIM with 50ms/s time quota and regions prioritization=
 on
> v5.15-rc5 Linux kernel with ZRAM swap device achieves 38.58% memory saving
> with only 1.94% runtime overhead.  For this, DAMON_RECLAIM consumes only
> 4.97% of single CPU time.

While it really consumes little CPU time, is it fine for `kdamond.0` to be =
in a=20
D (uninterruptible sleep) state all the time while active, pushing loadavg=
=20
over 1.0?

Thanks.

=2D-=20
Oleksandr Natalenko (post-factum)