From: Daniel Walker <dwalker@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interrupt starvation points
Date: 11 Feb 2005 09:36:42 -0800 [thread overview]
Message-ID: <1108143402.21935.83.camel@dhcp153.mvista.com> (raw)
In-Reply-To: <20050211173025.GA17387@elte.hu>
On Fri, 2005-02-11 at 09:30, Ingo Molnar wrote:
>
> i'm wondering what the best approach would be. Right now if
> DIRECT_PREEMPT is enabled [it's disabled currently] and a higher-prio
> task has been woken up we switch to it without ever enabling interrupts
> again. Re-enabling interrupts during schedule() will reduce irq
> latencies but will lengthen critical sections.
Yeah, it's a trade off .. The longest points that I observed involved
kernel threads like desched . Things that the scheduler() regularly
wakes up anyways. I would imagine there is an upper bound on the number
of tasks the scheduler can wake up.
Daniel
next prev parent reply other threads:[~2005-02-11 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 17:05 Daniel Walker
2005-02-11 17:30 ` Ingo Molnar
2005-02-11 17:36 ` Daniel Walker [this message]
2005-02-11 20:04 ` Russell King
2005-02-11 21:52 ` Daniel Walker
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=1108143402.21935.83.camel@dhcp153.mvista.com \
--to=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®