From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: 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>,
LKML <linux-kernel@vger.kernel.org>
Subject: [RFC 0/3] rt: Some fixes for migrate_disable/enable
Date: Fri, 16 Jun 2017 12:39:45 +0200 [thread overview]
Message-ID: <cover.1497607974.git.bristot@redhat.com> (raw)
This RFC suggest three changes from the migrate disable/enable
mechanism. Two of them are fixes, and the last one is a
suggestion/improvement.
As migrate_disable/enable is RT specific, this patch set is
RT specific.
Daniel Bristot de Oliveira (3):
rt: Increase/decrease the nr of migratable tasks when
enabling/disabling migration
rt: Update nr_cpus_allowed if the affinity of a task changes while its
migration is disabled
rt: Checks if task needs migration when re-enabling migration
kernel/sched/core.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 57 insertions(+), 1 deletion(-)
--
2.9.4
next reply other threads:[~2017-06-16 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 10:39 Daniel Bristot de Oliveira [this message]
2017-06-16 10:39 ` [RFC 1/3] rt: Increase/decrease the nr of migratable tasks when enabling/disabling migration Daniel Bristot de Oliveira
2017-06-16 10:39 ` [RFC 2/3] rt: Update nr_cpus_allowed if the affinity of a task changes while its migration is disabled Daniel Bristot de Oliveira
2017-06-16 10:39 ` [RFC 3/3] rt: Check if the task needs to migrate when re-enabling migration Daniel Bristot de Oliveira
2017-06-16 16:58 ` Sebastian Andrzej Siewior
2017-06-23 13:14 ` Sebastian Andrzej Siewior
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.1497607974.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.