From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: "Luis Claudio R . Goncalves" <lgoncalv@redhat.com>,
Clark Williams <williams@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] rt: Increase/decrease the nr of migratory tasks when enabling/disabling migration
Date: Wed, 21 Jun 2017 21:28:59 +0200 [thread overview]
Message-ID: <cover.1498068819.git.bristot@redhat.com> (raw)
This should be the v2 of the:
[RFC] rt: Some fixes for migrate_disable/enable
However, migrate_disable/enable was reworked during the
4.11-rt window, so it turns out that 2 of 3 problems were fixed.
Good! :-)
But there is still one problem, which is the dl/rt_nr_migratory inc/dec.
The problem is reproducible with the following command [in a 4 CPU box]:
# chrt -f 1 taskset -c 3 cat /dev/full | taskset -c 0-2 grep 'batman'
By applying only the patch 1/2, it is possible to see the problem with
the following command:
# cat /proc/sched_debug | grep rt_nr_migratory
.rt_nr_migratory : 18446744073709542849
.rt_nr_migratory : 18446744073709538566
.rt_nr_migratory : 18446744073709548257
.rt_nr_migratory : 0
The detailed description of the bug, and the fix, is in the log
of the patch 2/2.
Changes from RFC:
- The problems addressed in the patches:
x rt: Update nr_cpus_allowed if the affinity of a task changes while its
migration is disabled
x rt: Checks if task needs migration when re-enabling migration
were fixed, so these patches are not needed anymore, while patch:
x rt: Increase/decrease the nr of migratory tasks when
enabling/disabling migration
is still needed, so it was reworked for the new implementation.
- The patch showing the rt/dl_nr_migratory was added.
Daniel Bristot de Oliveira (2):
sched/debug: Inform the number of rt/dl task that can migrate
rt: Increase/decrease the nr of migratory tasks when
enabling/disabling migration
kernel/sched/core.c | 40 ++++++++++++++++++++++++++++++++--------
kernel/sched/debug.c | 15 +++++++++++++--
2 files changed, 45 insertions(+), 10 deletions(-)
--
2.9.4
next reply other threads:[~2017-06-21 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 19:28 Daniel Bristot de Oliveira [this message]
2017-06-21 19:29 ` [PATCH 1/2] sched/debug: Inform the number of rt/dl task that can migrate Daniel Bristot de Oliveira
2017-06-22 9:29 ` Ingo Molnar
2017-06-22 13:02 ` Daniel Bristot de Oliveira
2017-06-21 19:29 ` [PATCH 2/2] rt: Increase/decrease the nr of migratory tasks when enabling/disabling migration Daniel Bristot de Oliveira
2017-06-22 8:38 ` Ingo Molnar
2017-06-22 13:31 ` Daniel Bristot de Oliveira
2017-06-22 19:49 ` Ingo Molnar
2017-06-23 13:36 ` Daniel Bristot de Oliveira
2017-06-24 6:41 ` Ingo Molnar
2017-06-26 12:16 ` Daniel Bristot de Oliveira
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=cover.1498068819.git.bristot@redhat.com \
--to=bristot@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=lcapitulino@redhat.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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).