From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Venki Pallipadi <venki@google.com>, Paul Turner <pjt@google.com>,
Ingo Molnar <mingo@elte.hu>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] sched: fix nohz idle load balancer issues
Date: Thu, 29 Sep 2011 10:15:57 +0200 [thread overview]
Message-ID: <1317284157.22581.1.camel@twins> (raw)
In-Reply-To: <1317257264.11592.76.camel@sbsiddha-desk.sc.intel.com>
On Wed, 2011-09-28 at 17:47 -0700, Suresh Siddha wrote:
> So ended up with using kick_process() and the scheduler_ipi() context to
> trigger the SCHED_SOFTIRQ instead of using smp call function vector
> sequence (which has a deadlock scenario in the context of heavy
> interrupts which I can explain in detail when I send the complete
> changelog). And also I am explicitly requesting for idle balance to
> address the stale idle_at_tick condition.
I'd be interested in hearing more about that deadlock, because when
allocating your own csd and not waiting for the result
__smp_call_function_single() should be deadlock free.
> @@ -2733,6 +2733,11 @@ void scheduler_ipi(void)
> struct rq *rq = this_rq();
> struct task_struct *list = xchg(&rq->wake_list, NULL);
>
> + if (unlikely((rq->idle == current) && rq->nohz_balance_kick)) {
> + rq->idle_balance = 1;
> + raise_softirq_irqoff(SCHED_SOFTIRQ);
> + }
This can end up being outside of irq_enter()/irq_exit(), which is
probably not what you want. See the somewhat large comment right below
here.
next prev parent reply other threads:[~2011-09-29 8:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 11:50 Srivatsa Vaddagiri
2011-09-26 12:01 ` Srivatsa Vaddagiri
2011-09-27 6:32 ` Ingo Molnar
2011-09-27 10:31 ` Srivatsa Vaddagiri
2011-09-27 13:39 ` Ingo Molnar
2011-09-27 19:53 ` Venki Pallipadi
2011-09-27 23:49 ` Suresh Siddha
2011-09-28 4:15 ` Srivatsa Vaddagiri
2011-09-29 0:47 ` Suresh Siddha
2011-09-29 2:13 ` Srivatsa Vaddagiri
2011-09-29 8:15 ` Peter Zijlstra [this message]
2011-09-29 17:13 ` Suresh Siddha
2011-09-28 4:34 ` Srivatsa Vaddagiri
2011-09-28 4:39 ` Srivatsa Vaddagiri
2011-09-28 5:06 ` Srivatsa Vaddagiri
2011-09-28 14:17 ` Srivatsa Vaddagiri
2011-09-28 14:27 ` Srivatsa Vaddagiri
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=1317284157.22581.1.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pjt@google.com \
--cc=suresh.b.siddha@intel.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=vatsa@linux.vnet.ibm.com \
--cc=venki@google.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
Powered by JetHome