From: Bill Huey (hui) <bhuey@lnxw.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Kristian Benoit <kbenoit@opersys.com>,
linux-kernel@vger.kernel.org, paulmck@us.ibm.com, bhuey@lnxw.com,
andrea@suse.de, tglx@linutronix.de, karim@opersys.com,
pmarques@grupopie.com, bruce@andrew.cmu.edu,
nickpiggin@yahoo.com.au, ak@muc.de, sdietrich@mvista.com,
hch@infradead.org, akpm@osdl.org, rpm@xenomai.org
Subject: Re: PREEMPT_RT and I-PIPE: the numbers, part 4
Date: Sat, 9 Jul 2005 16:37:41 -0700 [thread overview]
Message-ID: <20050709233741.GA18435@nietzsche.lynx.com> (raw)
In-Reply-To: <1120929727.22337.15.camel@c-67-188-6-232.hsd1.ca.comcast.net>
On Sat, Jul 09, 2005 at 10:22:07AM -0700, Daniel Walker wrote:
> PREEMPT_RT is not pre-tuned for every situation , but the bests
> performance is achieved when the system is tuned. If any of these tests
> rely on a low priority thread, then we just raise the priority and you
> have better performance.
Just think about it. Throttling those threads via the scheduler throttles
the system in super controllable ways. This is very cool stuff. :)
bill
next prev parent reply other threads:[~2005-07-09 23:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 23:01 Kristian Benoit
2005-07-09 1:28 ` Karim Yaghmour
2005-07-09 7:19 ` Ingo Molnar
2005-07-09 15:39 ` Karim Yaghmour
2005-07-09 15:53 ` Karim Yaghmour
2005-07-09 15:53 ` Karim Yaghmour
2005-07-11 7:05 ` Ingo Molnar
2005-07-11 11:25 ` Karim Yaghmour
2005-07-09 17:22 ` Daniel Walker
2005-07-09 23:37 ` Bill Huey [this message]
2005-07-09 9:01 ` Paul Rolland
2005-07-09 14:47 ` Karim Yaghmour
2005-07-09 15:22 ` Ingo Molnar
2005-07-11 5:24 ` 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=20050709233741.GA18435@nietzsche.lynx.com \
--to=bhuey@lnxw.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=bruce@andrew.cmu.edu \
--cc=dwalker@mvista.com \
--cc=hch@infradead.org \
--cc=karim@opersys.com \
--cc=kbenoit@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=paulmck@us.ibm.com \
--cc=pmarques@grupopie.com \
--cc=rpm@xenomai.org \
--cc=sdietrich@mvista.com \
--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
Powered by JetHome