From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Cc: andrea@suse.de
Subject: Re: 2.4.18pre2aa1
Date: Wed, 9 Jan 2002 00:19:21 -0500 [thread overview]
Message-ID: <20020109001921.A11017@earthlink.net> (raw)
> I also couldn't resist to add the dyn_sched because I'm dealing with
> servers that needs to run 2k tasks (with only a few of them running at
> the same time loading cpu), so there the reclaculate loop was evil and
> the change is simple enough to be kind of obviously correct (btw: I also
Something has made a dramatic change in dbench throughput:
2.4.18pre2aa2 Throughput 23.4521 MB/sec (NB=29.3152 MB/sec 234.521 MBit/sec) 64 procs
2.4.17rc2aa2 Throughput 19.6605 MB/sec (NB=24.5756 MB/sec 196.605 MBit/sec) 64 procs
2.4.18pre2 Throughput 12.1986 MB/sec (NB=15.2483 MB/sec 121.986 MBit/sec) 64 procs
2.4.18pre2aa2 Throughput 18.6495 MB/sec (NB=23.3119 MB/sec 186.495 MBit/sec) 128 procs
2.4.17rc2aa2 Throughput 14.1212 MB/sec (NB=17.6515 MB/sec 141.212 MBit/sec) 128 procs
2.4.18pre2 Throughput 8.00551 MB/sec (NB=10.0069 MB/sec 80.0551 MBit/sec) 128 procs
2.4.18pre2aa2 Throughput 9.79641 MB/sec (NB=12.2455 MB/sec 97.9641 MBit/sec) 192 procs
2.4.18pre2 Throughput 8.09211 MB/sec (NB=10.1151 MB/sec 80.9211 MBit/sec) 192 procs
2.4.17rc2aa2 Throughput 5.80232 MB/sec (NB=7.2529 MB/sec 58.0232 MBit/sec) 192 procs
Some more test results for recent kernels are at:
http://home.earthlink.net/~rwhron/kernel/repo.html
> URL:
>
> ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.18pre2aa1.bz2
Based on the diff logs, here is a history of changes going into 2.4.18pre2aa1:
http://home.earthlink.net/~rwhron/kernel/2.4.18pre2aa1.html
--
Randy Hron
next reply other threads:[~2002-01-09 5:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 5:19 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-08 14:55 2.4.18pre2aa1 Andrea Arcangeli
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=20020109001921.A11017@earthlink.net \
--to=rwhron@earthlink.net \
--cc=andrea@suse.de \
--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