From: Trevor Woerner <twoerner.k@gmail.com>
To: Carlos Antunes <cmantunes@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: latency report
Date: Fri, 4 Nov 2005 11:04:21 -0500 [thread overview]
Message-ID: <569d37b00511040804y7289d623ocd13dd86a9c22082@mail.gmail.com> (raw)
In-Reply-To: <cb2ad8b50511040717k61bb560dsbe31a5c25f394bba@mail.gmail.com>
On 11/4/05, Carlos Antunes <cmantunes@gmail.com> wrote:
> rt2 was seriously screwed up (I posted about the problems in here).
> rt3 solved the problems. You might want to repeat your testing with at
> least rt3.
-rt3 lasted for all of, what, 30 minutes before -rt4 came out? :-)
I tested -rt5 last night and still have problems. I'm trying out -rt6
now. I was trying to isolate the problem but I haven't had any luck
yet.
If I boot a machine with 2.6.14-rt5 running either preemption k3 or
k4, simply running my "dolots.sh" script (which uses my "drone"
program, both of which are in the project package) will cause an OOM
problem after about 15 minutes or so. Running preemption setting k1
all night I found it was still happily running (and quite responsive
even with a loadavg of ~70) this morning.
Increasing the load to upwards to a loadavg of 200 with 2.6.14-rt5 k1
doesn't seem to have any problems.
I was anxious to get my results "out there" and since -rt5 was still
showing problems I decided to publish with -rt2 anyway (since most of
that work was already done). I made a note of the problems I
experience with these two settings in the report.
next prev parent reply other threads:[~2005-11-04 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 7:06 Trevor Woerner
2005-11-04 13:50 ` Gene Heskett
2005-11-04 14:44 ` Trevor Woerner
2005-11-04 15:42 ` Gene Heskett
2005-11-04 16:11 ` Randy.Dunlap
2005-11-04 15:17 ` Carlos Antunes
2005-11-04 16:04 ` Trevor Woerner [this message]
2005-11-04 16:20 ` Trevor Woerner
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=569d37b00511040804y7289d623ocd13dd86a9c22082@mail.gmail.com \
--to=twoerner.k@gmail.com \
--cc=cmantunes@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®