From: Qiliang Yuan <realwujing@gmail.com>
To: dev@lankhorst.se
Cc: cgroups@vger.kernel.org, dri-devel@lists.freedesktop.org,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
mkoutny@suse.com, mripard@kernel.org, natalie.vock@gmx.de,
tj@kernel.org
Subject: Re: [PATCH] cgroup/dmem: implement dmem.high soft limit and throttling
Date: Thu, 21 May 2026 19:28:19 +0800 [thread overview]
Message-ID: <20260521112819.62182-1-realwujing@gmail.com> (raw)
In-Reply-To: <63878874-39d2-43d5-9fc3-68addf9ebbdd@lankhorst.se>
Hello Maarten,
On Thu, May 21, 2026 at 09:45 AM Maarten Lankhorst wrote:
> It's the approach I'm more worried about. I believe that it's
> better if we punish exceeding their high limit by preferentially
> evicting those.
>
> It would make eviction run in 3 passes on the affected cgroup tree:
> - Round 1: Clients above their 'high' limit
> - Round 2: Clients above their 'low/min' limits
> - Round 3: Clients at or below their 'low' limit
Thank you for this concrete suggestion. This 3-pass eviction model is
exactly what's needed to make the dmem soft limit effective.
It addresses the core problem of providing a viable "recovery action" when
the limit is reached. By integrating these thresholds directly into the
TTM/dmem eviction weight calculation, we can achieve a more natural
over-subscription model.
I will rework the series for v2 to incorporate this hierarchy-aware
eviction logic.
Kind regards,
~Qiliang
next prev parent reply other threads:[~2026-05-22 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 6:07 [PATCH] cgroup/dmem: implement dmem.high soft limit and throttling Qiliang Yuan
2026-05-20 9:52 ` Tejun Heo
2026-05-21 11:28 ` Qiliang Yuan
2026-05-21 9:45 ` Maarten Lankhorst
2026-05-21 11:28 ` Qiliang Yuan [this message]
2026-05-21 10:52 ` Natalie Vock
2026-05-21 11:28 ` Qiliang Yuan
2026-05-25 12:14 ` Claude review: " Claude Code Review Bot
2026-05-25 12:14 ` Claude Code Review Bot
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=20260521112819.62182-1-realwujing@gmail.com \
--to=realwujing@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=mripard@kernel.org \
--cc=natalie.vock@gmx.de \
--cc=tj@kernel.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