From: Arjan van de Ven <arjan@infradead.org>
To: Donald Allen <donaldcallen@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: tickless scheduling
Date: Mon, 17 May 2010 07:29:53 -0700 [thread overview]
Message-ID: <20100517072953.64257f62@infradead.org> (raw)
In-Reply-To: <AANLkTin3tcYAsXVVEdhfPG0YJRYO6gcO-gCl1rlf6XNG@mail.gmail.com>
On Mon, 17 May 2010 10:11:51 -0400
Donald Allen <donaldcallen@gmail.com> wrote:
> On Mon, May 17, 2010 at 10:04 AM, Arjan van de Ven
> <arjan@infradead.org> wrote:
> > On Mon, 17 May 2010 09:44:47 -0400
> > Donald Allen <donaldcallen@gmail.com> wrote:
> >
> >> I will do the experiment suggested by Arjan van de Ven and report
> >> the results of that separately.
>
> Just for my own information, is this correct:
>
> I assume that tickless scheduling, rather than relying on periodic
> clock interrupts to wake up the scheduler, relies on interrupt
> handlers to somehow signal the system that the scheduler needs to run
> because they've just processed an event that has changed the state of
> the system?
well.. it relies on the hardware to signal the kernel that there's work
pending for a specific device.
technically this is true for both tickless and without tickless.
but without tickless there's so much activity in the system that it
never really goes quiet (and in fact, some different power management
decisions may be made because of that)
>
> If so, then it looks like using the msi-style device-specific
> interrupts isn't working reliably on this hardware? Or somehow the
that looks like a correct assumption to me.
> kernel (or a driver) is failing to handle the interrupts properly with
> msi enabled on certain hardware? I mention the latter only because of
> the report yesterday from someone else seeing the same symptoms I am
> on completely different hardware.
BIOSes breaking MSI is not entirely uncommon. Windows XP does not use
MSI for various things Linux does use MSI for, and so machines that come
with XP by default may not have this feature very well tested
unfortunately.
>
> /Don
>
> >
> >
> > since you're losing interrupts.. another good option to try is
> > "irqpoll"
> >
> >
> > --
> > Arjan van de Ven Intel Open Source Technology Centre
> > For development, discussion and tips for power savings,
> > visit http://www.lesswatts.org
> >
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2010-05-17 14:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 0:18 PROBLEM: tickless scheduling Donald Allen
2010-05-11 0:27 ` Robert Hancock
2010-05-11 0:34 ` Donald Allen
2010-05-11 0:38 ` Robert Hancock
2010-05-11 0:53 ` Donald Allen
2010-05-11 0:54 ` john stultz
2010-05-11 0:59 ` Donald Allen
2010-05-11 1:12 ` john stultz
2010-05-11 1:52 ` Donald Allen
2010-05-12 19:54 ` Donald Allen
2010-05-12 20:52 ` john stultz
2010-05-15 17:11 ` Donald Allen
2010-05-16 16:14 ` Stefan Biereigel
2010-05-16 20:41 ` Arjan van de Ven
2010-05-17 15:26 ` Donald Allen
2010-05-17 16:15 ` Stefan Biereigel
2010-05-16 23:36 ` Thomas Gleixner
2010-05-17 13:44 ` Donald Allen
2010-05-17 14:02 ` Donald Allen
2010-05-17 14:04 ` Arjan van de Ven
2010-05-17 14:11 ` Donald Allen
2010-05-17 14:29 ` Arjan van de Ven [this message]
2010-05-17 14:45 ` Donald Allen
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=20100517072953.64257f62@infradead.org \
--to=arjan@infradead.org \
--cc=donaldcallen@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).