From: Ed Tomlinson <tomlins@cam.org>
To: Neil Schemenauer <nascheme@enme.ucalgary.ca>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] page aging for 2.2.16
Date: Sun, 9 Jul 2000 11:30:45 -0400 [thread overview]
Message-ID: <00070911402500.02208@oscar> (raw)
In-Reply-To: <20000608031635.A353@acs.ucalgary.ca>
On Thu, 08 Jun 2000, Neil Schemenauer wrote:
> This patch seems to significantly improve the interactive
> performance of 2.2.16. Without the patch XMMS and the mouse
> pointer will stop responding for seconds at a time while running
> Bonnie. With the patch everything is smooth.
>
> I timed a kernel compile with -j 20 to test the cost of the
> aging. It does not seem to make a significant difference (3
> seconds slower). Bonnie reports slightly higher IO figures
> with the patch. I don't think the change is significant.
I have been running with with 2.2.17pre5 + this patch for the last
12 days with very good results. The reiserfs guys fixed a block
leak under high load and released 3.5.23. I want to rebuild my
kernel. I was thinking of 2.2.17pre10 + Marcelo Tosatti's merged
patch which includes
- balance dirty patch which wakes up kflushd at "correct" times. (Andrea)
- GFP-race-fix-2.patch, fixes the free_before_allocate issue without
hurting other cases. (Andrea)
- wait-dirty.patch, to avoid processes from waiting at dirty buffers while
there is freeable cache around. (me)
- WRITEA patch, fixes the interactiveness problem under high IO. (me)
along with the page aging stuff.
Is there a better combo?
Ed Tomlinson <tomlins@cam.org>
http://www.cam.org/~tomlins/njpipes.html
--
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/
prev parent reply other threads:[~2000-07-09 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-08 9:16 Neil Schemenauer
2000-06-08 12:41 ` Matthias Andree
2000-06-08 14:00 ` Stephen C. Tweedie
2000-07-09 15:30 ` Ed Tomlinson [this message]
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=00070911402500.02208@oscar \
--to=tomlins@cam.org \
--cc=linux-mm@kvack.org \
--cc=nascheme@enme.ucalgary.ca \
/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