From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Robert Love <rml@tech9.net>, Chris Mason <mason@suse.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Feedback on preemptible kernel patch
Date: Tue, 18 Sep 2001 06:06:06 +0200 [thread overview]
Message-ID: <20010918040550Z273827-761+10122@vger.kernel.org> (raw)
In-Reply-To: <200109140302.f8E32LG13400@zero.tech9.net> <200109150444.f8F4iEG19063@zero.tech9.net> <1000530869.32365.21.camel@phantasy>
In-Reply-To: <1000530869.32365.21.camel@phantasy>
[-- Attachment #1: Type: text/plain, Size: 5493 bytes --]
Am Samstag, 15. September 2001 07:14 schrieb Robert Love:
> On Sat, 2001-09-15 at 00:25, Dieter Nützel wrote:
> > > > > ReiserFS may be another problem.
> > > >
> > > > Can't wait for that.
> >
> > Most wanted, now.
>
> I am working on it, but I am unfamilar with it all.
>
> Are you seeing any specific problems, now? With the latest preemption
> patch on 2.4.10-pre9, do you crash? oops?
No, nothing with 2.4.10-pre9 + patch-rml-2.4.10-pre9-preempt-kernel-1 and
your MMX/3Dnow! fix.
2.4.10-pre10 + patch-rml-2.4.10-pre10-preempt-kernel-1 seems to be a winner!
See my results below.
> The only outstanding issue now is ReiserFS issues.
Yes, but no crash or oops for me.
"Only" some "stalls" during MPEG/Ogg-Vorbis playback (2-5 sec) :-(
> > It seems to be that kswap put some additional "load" on the disk from
> > time to time. Or is it the ReiserFS thing, again?
>
> I don't think its related to ReiserFS.
I think you are right.
> What sort of activity are you seeing? How often? How do you know its
> kswapd?
I saw it with "top" at the first line (but only some few percent).
It was during untarring some mid-sized archives (DRI) which took normally ~10
sec, but with kswap and 2.4.9-pre9+your patches ~30 sec. Even "sync" needed
some additional seconds.
Are there some reschedule/context switch (kernel lock release) statements
missing in ReiserFS?
Is this possible? Chris?
> I am glad the patch fixed it, the final version of that is going into
> the next preemption patch. Stay tuned.
I am very happy with patch-rml-2.4.10-pre10-preempt-kernel-1.
> These results are pretty good. Throughput seems down 2-3% in many
> cases, although latency is greatly improved. Look at those latency
> changes! From thousands of ms to hundreds of us in bonnie. Wow.
So look at my latest numbers. This time preempt only, sorry.
If you need 2.4.10-pre10 only, too please ask.
> Even if you don't care about latency (I'm not an audio person or
> anything), these changes should be worth it.
I do. Or better, one of my friend's father will do some digital video editing
with Linux:-)
> > Deleting with ReiserFS and the preempt kernel is GREAT!
>
> Good. I/O latency should be great now, with little change in
> throughput...
It is.
> > But I get some hiccup during noatun (mp3, ogg, etc. player for KDE-2.2)
> > or plaympeg together with dbench (16, 32). ReiserFS needs some preemption
> > fixes, too?
>
> You may still get some small hiccups ( < 1 second?) even with the
> preemption patch, as kernel locks prevent preemption (the patch can't
> guarentee low latency, just preemption outside of the locks).
Sadly 2-5 seconds at the beginning of dbench and during bonnie++ block
operations (huge IO pressure, ~20% system, 3-5% user, 116308 kilobytes paged
out).
> However, how bad was the hiccups with preemption disabled? I have heard
> reports where it is 3-5sec at times.
Yes, nearly the same.
> As the kernel becomes more scalable (finer-grain locking), preemption
> will improve. Past that, perhaps during 2.5, we can work on some other
> things to improve preemption.
Is this a ReiserFS only problem? Uninteruptable IO?
> > I've attached two small compressed bonnie++ HTML files.
>
> These were neat, thanks.
One more.
> Thank you for your feedback and support. Stay current with the kernel
> and the preemption patches,
I will.
> and I will try to figure the ReiserFS crashes out.
No crashes for me only the stalls.
Regards,
Dieter
2.4.10-pre10 + patch-rml-2.4.10-pre10-preempt-kernel-1
dbench-1.1 32
Throughput 26.2881 MB/sec (NB=32.8601 MB/sec 262.881 MBit/sec)
14.320u 54.140s 2:41.70 42.3% 0+0k 0+0io 911pf+0w
load: 2931
Throughput 27.3814 MB/sec (NB=34.2267 MB/sec 273.814 MBit/sec)
14.040u 55.920s 2:35.29 45.0% 0+0k 0+0io 911pf+0w
load: 2955
dbench 16
Throughput 32.9183 MB/sec (NB=41.1479 MB/sec 329.183 MBit/sec)
6.790u 26.580s 1:05.17 51.2% 0+0k 0+0io 511pf+0w
dbench 8
Throughput 34.8936 MB/sec (NB=43.617 MB/sec 348.936 MBit/sec)
3.300u 12.760s 0:31.27 51.3% 0+0k 0+0io 311pf+0w
dbench 4
Throughput 38.3568 MB/sec (NB=47.946 MB/sec 383.568 MBit/sec)
1.770u 6.160s 0:14.77 53.6% 0+0k 0+0io 211pf+0w
SunWave1>sync
dbench 2
Throughput 53.3066 MB/sec (NB=66.6333 MB/sec 533.066 MBit/sec)
0.940u 2.970s 0:05.95 65.7% 0+0k 0+0io 161pf+0w
dbench 1
Throughput 24.0354 MB/sec (NB=30.0442 MB/sec 240.354 MBit/sec)
0.470u 1.460s 0:06.49 29.7% 0+0k 0+0io 136pf+0w
Throughput 39.1102 MB/sec (NB=48.8878 MB/sec 391.102 MBit/sec)
0.400u 1.530s 0:04.38 44.0% 0+0k 0+0io 136pf+0w
Throughput 44.6889 MB/sec (NB=55.8611 MB/sec 446.889 MBit/sec)
0.500u 1.430s 0:03.96 48.7% 0+0k 0+0io 136pf+0w
Version 1.92a ------Sequential Output------ --Sequential Input-
--Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block--
--Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec
%CP
SunWave1 1248M 107 96 16513 21 9004 9 163 98 27844 18 256.9
3
Latency 115ms 2872ms 1743ms 121ms 64671us 3273ms
Version 1.92a ------Sequential Create------ --------Random
Create--------
SunWave1 -Create-- --Read--- -Delete-- -Create-- --Read---
-Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec
%CP
16 6029 69 +++++ +++ 13252 94 6762 82 +++++ +++ 11342
94
Latency 338ms 16041us 16309us 24248us 367us 17045us
load: 292
[-- Attachment #2: 2.4.10-pre10.html.bz2 --]
[-- Type: application/x-bzip2, Size: 908 bytes --]
next prev parent reply other threads:[~2001-09-18 4:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200109150444.f8F4iEG19063@zero.tech9.net>
[not found] ` <200109140302.f8E32LG13400@zero.tech9.net>
2001-09-14 4:35 ` Robert Love
2001-09-15 4:25 ` Dieter Nützel
2001-09-15 5:14 ` Robert Love
2001-09-18 4:06 ` Dieter Nützel [this message]
2001-09-18 8:35 ` Daniel Phillips
2001-09-18 18:18 ` Roger Larsson
2001-09-18 23:31 ` Robert Love
2001-09-20 6:40 ` Dieter Nützel
2001-09-18 23:31 ` Robert Love
2001-09-15 19:18 Robert Love
2001-09-16 1:28 ` Daniel Phillips
2001-09-16 1:54 ` Daniel Phillips
[not found] <Pine.LNX.4.33.0109140838040.21992-100000@sjoerd.sjoerdnet>
2001-09-14 15:04 ` Robert Love
2001-09-15 9:44 ` Arjan Filius
2001-09-15 10:38 ` Erik Mouw
2001-09-15 17:57 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-09-14 2:47 Dieter Nützel
2001-09-11 22:53 Robert Love
2001-09-08 5:22 grue
2001-09-08 5:47 ` Robert Love
2001-09-08 17:33 ` Arjan Filius
2001-09-08 18:22 ` safemode
2001-09-09 4:40 ` Robert Love
2001-09-09 17:09 ` Robert Love
2001-09-09 21:07 ` Arjan Filius
2001-09-09 21:26 ` Robert Love
2001-09-09 21:23 ` Arjan Filius
2001-09-09 21:37 ` Robert Love
2001-09-10 3:24 ` Daniel Phillips
2001-09-10 3:37 ` Jeremy Zawodny
2001-09-10 5:09 ` Robert Love
2001-09-10 18:25 ` Daniel Phillips
2001-09-10 21:29 ` Arjan Filius
2001-09-13 17:27 ` Robert Love
2001-09-14 7:30 ` george anzinger
2001-09-14 15:01 ` Robert Love
2001-09-11 19:47 ` Arjan Filius
2001-09-09 18:57 ` grue
2001-09-09 21:44 ` Robert Love
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=20010918040550Z273827-761+10122@vger.kernel.org \
--to=dieter.nuetzel@hamburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.com \
--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®