From: Ingo Molnar <mingo@elte.hu>
To: Con Kolivas <kernel@kolivas.org>
Cc: Andrew Morton <akpm@osdl.org>,
Nick Piggin <piggin@cyberone.com.au>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Likelihood of rt_tasks
Date: Fri, 9 Jul 2004 12:17:33 +0200 [thread overview]
Message-ID: <20040709101733.GA19011@elte.hu> (raw)
In-Reply-To: <40EE6CC2.8070001@kolivas.org>
* Con Kolivas <kernel@kolivas.org> wrote:
> While rt tasks are normally unlikely, what happens in the case when
> you are scheduling one or many running rt_tasks and the majority of
> your scheduling is rt? Would it be such a good idea in this setting
> that it is always hitting the slow path of branching all the time?
it's really not that big of an issue to hit the 'slow' path. And if it
is that common then the BTB of the CPU ought to cover it just fine.
Ingo
next prev parent reply other threads:[~2004-07-09 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 10:00 Likelihood of rt_tasks Con Kolivas
2004-07-09 10:17 ` Ingo Molnar [this message]
2004-07-09 23:53 ` Peter Williams
2004-07-10 0:16 ` Con Kolivas
2004-07-10 0:41 ` Peter Williams
2004-07-10 0:45 ` Con Kolivas
2004-07-10 11:15 ` Ingo Molnar
2004-07-10 12:05 ` Nick Piggin
2004-07-10 3:57 ` Elladan
2004-07-10 11:19 ` Ingo Molnar
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=20040709101733.GA19011@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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