From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
"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: Re: [PATCH 2/2] rt: Increase/decrease the nr of migratory tasks when enabling/disabling migration
Date: Mon, 26 Jun 2017 14:16:10 +0200 [thread overview]
Message-ID: <f7f9ee0a-706c-04d4-a21f-65bf6c214fde@redhat.com> (raw)
In-Reply-To: <20170624064157.tc7xogi4aa5t7maf@gmail.com>
On 06/24/2017 08:41 AM, Ingo Molnar wrote:
>> +enum inc_dec_migratory {
>> + DEC_NR_MIGRATORY = -1,
>> + INC_NR_MIGRATORY = 1,
>> +};
>> +
>> +static inline void
>> +inc_dec_nr_migratory(struct task_struct *p, enum inc_dec_migratory id)
>> +{
>> + if (unlikely((p->sched_class == &rt_sched_class ||
>> + p->sched_class == &dl_sched_class) &&
>> + p->nr_cpus_allowed > 1)) {
>> + if (p->sched_class == &rt_sched_class)
>> + task_rq(p)->rt.rt_nr_migratory += id;
>> + else
>> + task_rq(p)->dl.dl_nr_migratory += id;
>> + }
>> +}
> How about just 'long delta', pass in +1 or -1 and do away with the
> inc_dec_migratory complication?
Ack! I am cooking a v2 using a long delta, rather than the
inc_dec_migratory complication (yeah, I exaggerated hehe).
Thanks!
-- Daniel
prev parent reply other threads:[~2017-06-26 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 19:28 [PATCH 0/2] rt: Increase/decrease the nr of migratory tasks when enabling/disabling migration Daniel Bristot de Oliveira
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 [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=f7f9ee0a-706c-04d4-a21f-65bf6c214fde@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).