From: Andrew Morton <akpm@linux-foundation.org>
To: Kevin Hao <haokexin@gmail.com>
Cc: linux-mm@kvack.org, "Rafael J. Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] mm/khugepaged: Remove unnecessary try_to_freeze()
Date: Mon, 18 Dec 2023 10:34:51 -0800 [thread overview]
Message-ID: <20231218103451.fd11a2179a01d622cea01858@linux-foundation.org> (raw)
In-Reply-To: <20231216114341.2281852-1-haokexin@gmail.com>
On Sat, 16 Dec 2023 19:43:41 +0800 Kevin Hao <haokexin@gmail.com> wrote:
> A freezable kernel thread can enter frozen state during freezing by
> either calling try_to_freeze() or using wait_event_freezable() and its
> variants. However, there is no need to use both methods simultaneously.
> The freezable wait variants have been used in khugepaged_wait_work()
> and khugepaged_alloc_sleep(), so remove this unnecessary
> try_to_freeze().
>
Looks OK to me, but this will increase freezing latencies. How
significant is this?
Also, we already have a patch from you with this same title. Please
try to use different titles for different patches.
next prev parent reply other threads:[~2023-12-18 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 11:43 Kevin Hao
2023-12-18 18:34 ` Andrew Morton [this message]
2023-12-19 0:44 ` Kevin Hao
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=20231218103451.fd11a2179a01d622cea01858@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=haokexin@gmail.com \
--cc=linux-mm@kvack.org \
--cc=pavel@ucw.cz \
--cc=rafael@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