From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "David S. Miller" <davem@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: [PATCH *] VM patch for 2.4.0-test8
Date: Fri, 15 Sep 2000 19:28:43 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0009151915040.7748-100000@tux.rsn.hk-r.se> (raw)
In-Reply-To: <Pine.LNX.4.21.0009141351510.10822-100000@duckman.distro.conectiva>
On Thu, 14 Sep 2000, Rik van Riel wrote:
> On Wed, 13 Sep 2000, David S. Miller wrote:
>
> > In page_launder() about halfway down there is this sequence of tests
> > on LRU pages:
> >
> > if (!clearedbuf) {
> > ...
> > } else if (!page->mapping) {
> > ...
> > } else if (page_count(page) > 1) {
> > } else /* page->mapping && page_count(page) == 1 */ {
> > ...
> > }
> >
> > Above this sequence we've done a page_cache_get.
>
> Indeed, you're right. This bug certainly explains some
> of the performance things I've seen in the stress test
> last night...
>
> Btw, in case you're wondering ... the box /survived/
> a stress test that would get programs killed on quite
> a few "stable" kernels we've been shipping lately. ;)
Here comes a success report.
I've been using 2.4.0test8+2.4.0-t8-vmpatch2 for about a day now and the
performance is great.
I've just bought a new harddrive and I was copying a _lot_ of data to the
new drive and didn't notice anything axcept the HDD led flashing :)
And now I helped a friend back up his data while he converts to reiserfs.
I had a stream of 7-9MB/s down to my harddrive for quite a while and still
didn't notice anything. Everything ended up on the inactive list.
I've been trying to get my machine to swap but that seems hard with this
new patch :) I have 0kB of swap used after 8h uptime, and I have been
compiling, moving files between partitions and running md5sum on files
(that was a big problem before, everything ended up on the active list and
the swapping started and brought my machine down to a crawl)
I can mention that while backing up my friends data I had 7000-9000
interrupts per second and 10 000 - 12 000 context switches per second.
I was really impressed that I didn't notice anything. I remember that my
machine was terribly slow when it did over 5000 context switches with
vanilla test6.
(My machine is a pIII 700 with 256MB ram)
If anyone want more info or anything please feel free to mail me.
(Hopefully my mailserver is up, we've been experiencing some power
problems)
/Martin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-09-15 17:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-14 4:30 Rik van Riel
2000-09-14 5:25 ` David S. Miller
2000-09-14 6:11 ` Juan J. Quintela
2000-09-14 8:18 ` David S. Miller
2000-09-14 16:53 ` Rik van Riel
2000-09-14 17:49 ` Rik van Riel
2000-09-15 17:28 ` Martin Josefsson [this message]
2000-09-15 19:37 ` Jamie Lokier
2000-09-15 21:07 ` David Ford
2000-09-15 22:04 ` Rik van Riel
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=Pine.LNX.4.21.0009151915040.7748-100000@tux.rsn.hk-r.se \
--to=gandalf@wlug.westbo.se \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.com \
/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