From: Michal Hocko <mhocko@suse.com>
To: Kaitao Cheng <kaitao.cheng@linux.dev>
Cc: Dennis Zhou <dennis@kernel.org>, Pedro Falcato <pfalcato@suse.de>,
akpm@linux-foundation.org, tj@kernel.org, cl@gentwo.org,
vbabka@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, muchun.song@linux.dev,
Kaitao Cheng <chengkaitao@kylinos.cn>
Subject: Re: [PATCH 1/2] mm/percpu: Preserve NOFS/NOIO scope during chunk create and populate
Date: Mon, 1 Jun 2026 17:45:19 +0200 [thread overview]
Message-ID: <ah2pD468y1LCIe3G@tiehlicka> (raw)
In-Reply-To: <e315d2a9-5069-4a8d-a0b5-7c0033ee46ba@linux.dev>
On Mon 01-06-26 10:27:53, Kaitao Cheng wrote:
> However, if we revert 9a5b183941b, it seems that all of these issues would
> be resolved. The only downside is that the failure rate of pcpu_alloc_noprof()
> allocations may increase, which might be acceptable.
That has practical impact on some versions of iscsid which do not have
PR_SET_IO_FLUSHER. And maybe some more so I would rather not revert
based on a theoretical concerns which I believe is the case here.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2026-06-01 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 13:29 [PATCH 0/2] mm/percpu: Fix possible NOFS/NOIO reclaim recursion Kaitao Cheng
2026-05-28 13:29 ` [PATCH 1/2] mm/percpu: Preserve NOFS/NOIO scope during chunk create and populate Kaitao Cheng
2026-05-29 9:25 ` Pedro Falcato
2026-05-29 9:38 ` Pedro Falcato
2026-05-30 12:47 ` Kaitao Cheng
2026-05-30 13:32 ` Dennis Zhou
2026-06-01 2:27 ` Kaitao Cheng
2026-06-01 15:45 ` Michal Hocko [this message]
2026-06-02 3:03 ` Kaitao Cheng
2026-05-28 13:29 ` [PATCH 2/2] mm/percpu: Avoid pcpu_alloc_mutex recursion from reclaim Kaitao Cheng
2026-05-29 9:34 ` Pedro Falcato
2026-05-28 21:09 ` [PATCH 0/2] mm/percpu: Fix possible NOFS/NOIO reclaim recursion Andrew Morton
2026-05-28 21:10 ` Andrew Morton
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=ah2pD468y1LCIe3G@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=chengkaitao@kylinos.cn \
--cc=cl@gentwo.org \
--cc=dennis@kernel.org \
--cc=kaitao.cheng@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=pfalcato@suse.de \
--cc=tj@kernel.org \
--cc=vbabka@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