[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <zxorog2mv54v5dpl5cmmkd3j4hznyxbj435hjtbtzljwspm6mt@tj446cjrclcg>
Date: Tue, 27 May 2025 09:54:10 -0700
From: Shakeel Butt <shakeel.butt@...ux.dev>
To: Breno Leitao <leitao@...ian.org>
Cc: Johannes Weiner <hannes@...xchg.org>, Michal Hocko <mhocko@...nel.org>,
Roman Gushchin <roman.gushchin@...ux.dev>, Muchun Song <muchun.song@...ux.dev>,
Andrew Morton <akpm@...ux-foundation.org>, Chen Ridong <chenridong@...wei.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Michal Hocko <mhocko@...e.com>, cgroups@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org, kernel-team@...a.com,
Michael van der Westhuizen <rmikey@...a.com>, Usama Arif <usamaarif642@...il.com>,
Pavel Begunkov <asml.silence@...il.com>, Rik van Riel <riel@...riel.com>
Subject: Re: [PATCH] memcg: Always call cond_resched() after fn()
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.
Powered by blists - more mailing lists