From: Charan Teja Reddy <charante@codeaurora.org>
To: akpm@linux-foundation.org, vbabka@suse.cz, nigupta@nvidia.com,
hannes@cmpxchg.org, corbet@lwn.net, mcgrof@kernel.org,
keescook@chromium.org, yzaikin@google.com, aarcange@redhat.com,
cl@linux.com, xi.fengfei@h3c.com, mchehab+huawei@kernel.org,
andrew.a.klychkov@gmail.com, dave.hansen@linux.intel.com,
bhe@redhat.com, iamjoonsoo.kim@lge.com, mateusznosek0@gmail.com,
sh_def@163.com, vinmenon@codeaurora.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Charan Teja Reddy <charante@codeaurora.org>
Subject: [PATCH v3 2/2] mm: compaction: fix wakeup logic of proactive compaction
Date: Mon, 31 May 2021 16:24:52 +0530 [thread overview]
Message-ID: <ad2600f3d8d7c0d44b35d9fad0031d82c5a3c285.1622454385.git.charante@codeaurora.org> (raw)
In-Reply-To: <cover.1622454385.git.charante@codeaurora.org>
In-Reply-To: <cover.1622454385.git.charante@codeaurora.org>
Currently, proactive compaction tries to get triggered for every
HPAGE_FRAG_CHECK_INTERVAL_MSEC(=500msec) even when proactive compaction
is disabled with sysctl.compaction_proactiveness = 0. This results in
kcompactd thread wakes up and goes to sleep for every 500msec with out
the need of doing proactive compaction. Though this doesn't have any
overhead, few cpu cycles can be saved by avoid of waking up kcompactd
thread for proactive compaction when it is disabled.
Signed-off-by: Charan Teja Reddy <charante@codeaurora.org>
---
- This patch is newly raised in V3, thus no changes exist in V1 and V2
mm/compaction.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/mm/compaction.c b/mm/compaction.c
index 197e203..0edcd0f 100644
--- a/mm/compaction.c
+++ b/mm/compaction.c
@@ -2926,11 +2926,14 @@ static int kcompactd(void *p)
while (!kthread_should_stop()) {
unsigned long pflags;
+ long timeout;
+ timeout = sysctl_compaction_proactiveness ?
+ msecs_to_jiffies(HPAGE_FRAG_CHECK_INTERVAL_MSEC) :
+ MAX_SCHEDULE_TIMEOUT;
trace_mm_compaction_kcompactd_sleep(pgdat->node_id);
if (wait_event_freezable_timeout(pgdat->kcompactd_wait,
- kcompactd_work_requested(pgdat),
- msecs_to_jiffies(HPAGE_FRAG_CHECK_INTERVAL_MSEC)) &&
+ kcompactd_work_requested(pgdat), timeout) &&
!pgdat->proactive_compact_trigger) {
psi_memstall_enter(&pflags);
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member of the Code Aurora Forum, hosted by The Linux Foundation
prev parent reply other threads:[~2021-05-31 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 10:54 [PATCH V3 0/2] mm: compaction: proactive compaction trigger by user Charan Teja Reddy
2021-05-31 10:54 ` [PATCH v3 1/2] mm: compaction: support triggering of proactive compaction " Charan Teja Reddy
2021-06-07 10:38 ` Charan Teja Kalla
2021-06-14 14:57 ` Charan Teja Kalla
2021-06-16 11:59 ` Vlastimil Babka
2021-06-17 7:30 ` Charan Teja Kalla
2021-06-17 14:37 ` Vlastimil Babka
2021-06-17 16:05 ` Charan Teja Kalla
2021-06-17 16:17 ` Vlastimil Babka
2021-05-31 10:54 ` Charan Teja Reddy [this message]
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=ad2600f3d8d7c0d44b35d9fad0031d82c5a3c285.1622454385.git.charante@codeaurora.org \
--to=charante@codeaurora.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.a.klychkov@gmail.com \
--cc=bhe@redhat.com \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mateusznosek0@gmail.com \
--cc=mcgrof@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nigupta@nvidia.com \
--cc=sh_def@163.com \
--cc=vbabka@suse.cz \
--cc=vinmenon@codeaurora.org \
--cc=xi.fengfei@h3c.com \
--cc=yzaikin@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;
as well as URLs for NNTP newsgroup(s).