From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Thomas Gleixner <tglx@linutronix.de>,
Mike Galbraith <bitbucket@online.de>, X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Too many rescheduling interrupts (still!)
Date: Wed, 12 Feb 2014 19:15:17 +0100 [thread overview]
Message-ID: <20140212181517.GE27965@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140212174637.GC5496@localhost.localdomain>
On Wed, Feb 12, 2014 at 06:46:39PM +0100, Frederic Weisbecker wrote:
> Ok but if the target is idle, dynticks and not polling, we don't have the choice
> but to send an IPI, right? I'm talking about this kind of case.
Yes; but Andy doesn't seem concerned with such hardware (!x86).
Anything x86 (except ancient stuff) is effectively polling and wakes up
from the TIF_NEED_RESCHED write.
prev parent reply other threads:[~2014-02-12 18:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 20:23 Too many rescheduling interrupts (still!) Andy Lutomirski
2014-02-11 21:21 ` Thomas Gleixner
2014-02-11 22:34 ` Andy Lutomirski
2014-02-12 10:13 ` Peter Zijlstra
2014-02-12 15:49 ` Andy Lutomirski
2014-02-12 16:39 ` Peter Zijlstra
2014-02-12 18:19 ` Andy Lutomirski
2014-02-12 20:17 ` Peter Zijlstra
2014-02-13 1:40 ` [RFC] sched: Add a new lockless wake-from-idle implementation Andy Lutomirski
2014-02-13 9:38 ` Ingo Molnar
2014-02-13 14:49 ` Frederic Weisbecker
2014-02-13 14:50 ` Peter Zijlstra
2014-02-13 17:07 ` Andy Lutomirski
2014-02-13 20:16 ` Peter Zijlstra
2014-02-13 20:35 ` Andy Lutomirski
2014-02-13 19:58 ` Andy Lutomirski
2014-02-14 1:38 ` Andy Lutomirski
2014-02-14 20:01 ` Andy Lutomirski
2014-02-14 20:17 ` Andy Lutomirski
2014-02-14 21:19 ` Peter Zijlstra
2014-02-12 15:59 ` Too many rescheduling interrupts (still!) Frederic Weisbecker
2014-02-12 16:43 ` Peter Zijlstra
2014-02-12 17:46 ` Frederic Weisbecker
2014-02-12 18:15 ` Peter Zijlstra [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=20140212181517.GE27965@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bitbucket@online.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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