From: Hillf Danton <hdanton@sina.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Yu Zhao <yuzhao@google.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Chris Down <chris@chrisdown.name>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: MGLRU premature memcg OOM on slow writes
Date: Wed, 13 Mar 2024 18:59:53 +0800 [thread overview]
Message-ID: <20240313105953.2234-1-hdanton@sina.com> (raw)
In-Reply-To: <20240312210822.GB65481@cmpxchg.org>
On Tue, 12 Mar 2024 17:08:22 -0400 Johannes Weiner <hannes@cmpxchg.org>
>
> Back to the broader question though: if reclaim demand outstrips clean
> pages and the only viable candidates are dirty ones (e.g. an
> allocation spike in the presence of dirty/writeback pages), there only
> seem to be 3 options:
>
> 1) sleep-wait for writeback
> 2) continue scanning, aka busy-wait for writeback + age inversions
> 3) find nothing and declare OOM
4) make dirty ratio match your writeback bandwidth [1]
[1] Subject: Re: 4.8.8 kernel trigger OOM killer repeatedly when I have lots of RAM that should be free
https://lore.kernel.org/lkml/CA+55aFzNe=3e=cDig+vEzZS5jm2c6apPV4s5NKG4eYL4_jxQjQ@mail.gmail.com/
next prev parent reply other threads:[~2024-03-13 11:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 2:31 Chris Down
2024-02-29 17:28 ` Chris Down
2024-02-29 23:51 ` Axel Rasmussen
2024-03-01 0:30 ` Chris Down
2024-03-08 19:18 ` Axel Rasmussen
2024-03-08 21:22 ` Johannes Weiner
2024-03-11 9:11 ` Yafang Shao
2024-03-12 16:44 ` Axel Rasmussen
2024-03-12 20:07 ` Yu Zhao
2024-03-12 20:11 ` Yu Zhao
2024-03-13 3:33 ` Yafang Shao
2024-03-14 22:23 ` Yu Zhao
2024-03-15 2:38 ` Yafang Shao
2024-03-15 14:27 ` Johannes Weiner
2024-03-12 21:08 ` Johannes Weiner
2024-03-13 2:08 ` Yu Zhao
2024-03-13 3:22 ` Johannes Weiner
2024-03-13 10:59 ` Hillf Danton [this message]
2024-03-01 11:25 ` Hillf Danton
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=20240313105953.2234-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=axelrasmussen@google.com \
--cc=cgroups@vger.kernel.org \
--cc=chris@chrisdown.name \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yuzhao@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox