From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Robert Love <rml@tech9.net>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: I3 sched brakes "realtime" task
Date: Thu, 17 Jan 2002 10:17:12 +0100 [thread overview]
Message-ID: <20020117091722Z288420-13996+7423@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0201170008290.20808-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0201170008290.20808-100000@localhost.localdomain>
On Thursday, 17. January 2002 00:09, you wrote:
> On Wed, 16 Jan 2002, Dieter [iso-8859-15] Nützel wrote:
> > running I3 on top of 2.4.18-pre3-I3-VM-22-preempt-lock ;-) This
> > combination rouks!
>
> could you try the -J0 patch i've just uploaded? It has a number of fixes
> and improvements.
Somewhat better but a reniced artsd (-16 or -19) stutters a little during
dbench 32. Maybe there is one show stopper slipped into preempt or lock-break
during my 10_vm-22 merge. Few stalls during heavy IO. But I have the buffer.c
fix applied.
2.4.18-pre4-J0-VM-22-preempt-lock
32 clients started
................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................+..+...................................................................+..+.+.+.++++.++.+...........++...........++...+.+++.+++.........+...+.++.....+...++....+********************************
Throughput 51.711 MB/sec (NB=64.6388 MB/sec 517.11 MBit/sec)
14.260u 49.860s 1:22.71 77.5% 0+0k 0+0io 939pf+0w
More to come after some sleep...
-Dieter
BTW I'll prepare a unified patch for wider testing if anybody want.
next parent reply other threads:[~2002-01-17 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0201170008290.20808-100000@localhost.localdomain>
2002-01-17 9:17 ` Dieter Nützel [this message]
2002-01-16 21:10 Dieter Nützel
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=20020117091722Z288420-13996+7423@vger.kernel.org \
--to=dieter.nuetzel@hamburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
/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®