From: Sudarshan Rajagopalan <quic_sudaraja@quicinc.com>
To: David Hildenbrand <david@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Suren Baghdasaryan <surenb@google.com>,
Mike Rapoport <rppt@kernel.org>,
Oscar Salvador <osalvador@suse.de>,
Anshuman Khandual <anshuman.khandual@arm.com>,
mark.rutland@arm.com, will@kernel.org,
virtualization@lists.linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Cc: Sudarshan Rajagopalan <quic_sudaraja@quicinc.com>,
Trilok Soni <quic_tsoni@quicinc.com>,
Sukadev Bhattiprolu <quic_sukadev@quicinc.com>,
Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>,
Patrick Daly <quic_pdaly@quicinc.com>
Subject: [PATCH] psi: reduce min window size to 50ms
Date: Fri, 10 Feb 2023 14:31:02 -0800 [thread overview]
Message-ID: <8b7a3270fe253de1cd2b71473e29394409b2a0f7.1676067791.git.quic_sudaraja@quicinc.com> (raw)
In-Reply-To: <cover.1676067791.git.quic_sudaraja@quicinc.com>
In-Reply-To: <cover.1676067791.git.quic_sudaraja@quicinc.com>
Few systems would require much finer-grained tracking of memory
pressure in the system using PSI mechanism. Reduce the minimum
allowable window size to be 50ms to increase the sampling rate
of PSI monitor for much faster response and reaction to memory
pressures in the system. With 50ms window size, the smallest
resolution of memory pressure that can be tracked is now 5ms.
Signed-off-by: Sudarshan Rajagopalan <quic_sudaraja@quicinc.com>
---
kernel/sched/psi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/psi.c b/kernel/sched/psi.c
index ee2ecc0..6eabf27 100644
--- a/kernel/sched/psi.c
+++ b/kernel/sched/psi.c
@@ -160,7 +160,7 @@ __setup("psi=", setup_psi);
#define EXP_300s 2034 /* 1/exp(2s/300s) */
/* PSI trigger definitions */
-#define WINDOW_MIN_US 500000 /* Min window size is 500ms */
+#define WINDOW_MIN_US 50000 /* Min window size is 50ms */
#define WINDOW_MAX_US 10000000 /* Max window size is 10s */
#define UPDATES_PER_WINDOW 10 /* 10 updates per window */
--
2.7.4
next prev parent reply other threads:[~2023-02-10 22:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 22:31 Sudarshan Rajagopalan
2023-02-10 22:31 ` Sudarshan Rajagopalan [this message]
2023-02-10 23:03 ` Suren Baghdasaryan
2023-02-11 0:44 ` Sudarshan Rajagopalan
2023-02-11 1:09 ` Suren Baghdasaryan
2023-02-11 1:46 ` Sudarshan Rajagopalan
2023-02-11 2:13 ` Suren Baghdasaryan
2023-02-14 2:12 ` Sudarshan Rajagopalan
2023-02-14 19:34 ` Suren Baghdasaryan
2023-02-24 12:47 ` Michal Hocko
2023-02-24 21:07 ` Suren Baghdasaryan
2023-02-27 13:34 ` Michal Hocko
2023-02-27 17:49 ` Suren Baghdasaryan
2023-02-27 19:11 ` Michal Hocko
2023-02-27 19:50 ` Suren Baghdasaryan
2023-02-28 13:50 ` Michal Hocko
2023-02-28 18:18 ` Suren Baghdasaryan
2023-03-01 1:49 ` Suren Baghdasaryan
2023-02-27 19:19 ` Josh Hunt
2023-02-27 19:51 ` Suren Baghdasaryan
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=8b7a3270fe253de1cd2b71473e29394409b2a0f7.1676067791.git.quic_sudaraja@quicinc.com \
--to=quic_sudaraja@quicinc.com \
--cc=anshuman.khandual@arm.com \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=osalvador@suse.de \
--cc=quic_pdaly@quicinc.com \
--cc=quic_sukadev@quicinc.com \
--cc=quic_svaddagi@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=will@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