From: Shakeel Butt <shakeel.butt@linux.dev>
To: Breno Leitao <leitao@debian.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Chen Ridong <chenridong@huawei.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michal Hocko <mhocko@suse.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
Michael van der Westhuizen <rmikey@meta.com>,
Usama Arif <usamaarif642@gmail.com>,
Pavel Begunkov <asml.silence@gmail.com>,
Rik van Riel <riel@surriel.com>
Subject: Re: [PATCH] memcg: Always call cond_resched() after fn()
Date: Tue, 27 May 2025 09:54:10 -0700 [thread overview]
Message-ID: <zxorog2mv54v5dpl5cmmkd3j4hznyxbj435hjtbtzljwspm6mt@tj446cjrclcg> (raw)
In-Reply-To: <aDWN9mP3wPQnwo4m@gmail.com>
On Tue, May 27, 2025 at 03:03:34AM -0700, Breno Leitao wrote:
>
> Not sure I followed you here. __oom_kill_process is doing the following:
>
> static void __oom_kill_process(struct task_struct *victim, const char *message)
> {
> ...
> pr_err("%s: Killed process %d (%s) total-vm:%lukB, anon-rss:%lukB, file-rss:%lukB, shmem-rss:%lukB, UID:%u pgtables:%lukB oom_score_adj:%hd\n",
>
>
> Would you use a buffer to print to, and them flush it at the same time
> (with pr_err()?)
>
Something similar to what mem_cgroup_print_oom_meminfo() does with
seq_buf.
next prev parent reply other threads:[~2025-05-27 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 17:21 Breno Leitao
2025-05-23 18:21 ` Shakeel Butt
2025-05-27 10:03 ` Breno Leitao
2025-05-27 16:54 ` Shakeel Butt [this message]
2025-05-28 9:18 ` Breno Leitao
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=zxorog2mv54v5dpl5cmmkd3j4hznyxbj435hjtbtzljwspm6mt@tj446cjrclcg \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=asml.silence@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=riel@surriel.com \
--cc=rmikey@meta.com \
--cc=roman.gushchin@linux.dev \
--cc=usamaarif642@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox