From: Lee Revell <rlrevell@joe-job.com>
To: Mark_H_Johnson@raytheon.com
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
Bill Huey <bhuey@lnxw.com>,
linux-kernel@vger.kernel.org, Rui Nuno Capela <rncbc@rncbc.org>,
"K.R. Foley" <kr@cybsft.com>, Adam Heath <doogie@debian.org>,
Florian Schmidt <mista.tapas@gmx.net>,
Thomas Gleixner <tglx@linutronix.de>,
Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Real-Time Preemption, comparison to 2.6.10-mm1
Date: Tue, 04 Jan 2005 16:37:16 -0500 [thread overview]
Message-ID: <1104874637.8850.3.camel@krustophenia.net> (raw)
In-Reply-To: <OF57960072.EA98312D-ON86256F7F.006EF463-86256F7F.006EF501@raytheon.com>
On Tue, 2005-01-04 at 14:11 -0600, Mark_H_Johnson@raytheon.com wrote:
> The non RT application starvation for mm1 was much less
> pronounced but still present. I could watch the disk light
> on the last two tests & see it go out (and stay out) for an
> extended period. It does not make sense to me that a single RT
> application (on a two CPU machine) and a nice'd non RT application
> can cause this starvation behavior. This behavior was not
> present on the 2.4 kernels and seems to be a regression to me.
I think I am seeing this problem too. It doesn't just apply to RT
tasks, it seems that CPU bound tasks starve each other. I noticed that
with the RT kernel, a kernel compile or dpkg will starve evolution, to
the point where it takes 30 seconds to display a message. If I go and
background the CPU hog, the message renders _instantly_.
It's definitely present with 2.6.10-rc2 + RT (PK config) and absent with
2.6.10 vanilla. I need to figure out whether -mm has the problem.
Lee
next prev parent reply other threads:[~2005-01-04 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 20:11 Real-Time Preemption, comparison to 2.6.10-mm1 Mark_H_Johnson
2005-01-04 21:37 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-05 13:55 Mark_H_Johnson
2005-01-05 14:38 ` K.R. Foley
2005-01-05 17:52 Mark_H_Johnson
2005-01-05 21:20 ` K.R. Foley
2005-01-05 22:58 Mark_H_Johnson
2005-01-07 0:48 ` K.R. Foley
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=1104874637.8850.3.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=Mark_H_Johnson@raytheon.com \
--cc=akpm@osdl.org \
--cc=bhuey@lnxw.com \
--cc=doogie@debian.org \
--cc=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mista.tapas@gmx.net \
--cc=nando@ccrma.Stanford.EDU \
--cc=rncbc@rncbc.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.