From: l@dorileo.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt@goodmis.org, John Kacur <jkacur@redhat.com>,
linux-mm@kvack.org,
Leandro Dorileo <leandro.maciel.dorileo@intel.com>
Subject: [RFC][4.1.15-rt17 PATCH] mm: swap: lru drain don't use workqueue with PREEMPT_RT_FULL
Date: Sun, 10 Jan 2016 22:43:21 -0200 [thread overview]
Message-ID: <1452473001-10518-1-git-send-email-l@dorileo.org> (raw)
From: Leandro Dorileo <leandro.maciel.dorileo@intel.com>
Running a smp system with an -rt kernel, with CONFIG_PREEMPT_RT_FULL,
in a heavy cpu load scenario and an arbitrary process tries to mlockall
with MCL_CURRENT flag that process will block indefinitely - until the
process resulting in the heavy cpu load finishes(the process's set the
sched priority > 0).
Since MCL_CURRENT flag is passed to mlockall it will try to drain the
lru in all cpus. The lru_add_drain_all() will start an workqueue to
drain lru on each online cpu and then try to flush the work(will wait
until the work's finished).
The drain for the heavy loaded core will never finished - like
mentioned before - until the process resulting in the heavy cpu load
finishes. The work will never be scheduled, even if the calling process
has been so.
This patch adds an lru_add_drain_all() implementation for such
situation, and synchronously do the lru drain on behalf of the calling
process.
Signed-off-by: Leandro Dorileo <leandro.maciel.dorileo@intel.com>
---
mm/swap.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/mm/swap.c b/mm/swap.c
index 1785ac6..df807b4 100644
--- a/mm/swap.c
+++ b/mm/swap.c
@@ -864,6 +864,23 @@ void lru_add_drain(void)
local_unlock_cpu(swapvec_lock);
}
+#ifdef CONFIG_PREEMPT_RT_FULL
+void lru_add_drain_all(void)
+{
+ static DEFINE_MUTEX(lock);
+ int cpu;
+
+ mutex_lock(&lock);
+ get_online_cpus();
+
+ for_each_online_cpu(cpu) {
+ smp_call_function_single(cpu, lru_add_drain, NULL, 1);
+ }
+
+ put_online_cpus();
+ mutex_unlock(&lock);
+}
+#else
static void lru_add_drain_per_cpu(struct work_struct *dummy)
{
lru_add_drain();
@@ -900,6 +917,7 @@ void lru_add_drain_all(void)
put_online_cpus();
mutex_unlock(&lock);
}
+#endif
/**
* release_pages - batched page_cache_release()
--
2.7.0
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2016-01-11 0:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 0:43 l [this message]
2016-01-12 12:01 ` Thomas Gleixner
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=1452473001-10518-1-git-send-email-l@dorileo.org \
--to=l@dorileo.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=leandro.maciel.dorileo@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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