From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: linux-mm <linux-mm@kvack.org>
Cc: linux-kernel <linux-kernel@vger.rutgers.edu>
Subject: report [PATCH] buffermem limit
Date: Thu, 12 Mar 1998 17:37:12 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.980312173402.664A-100000@mirkwood.dummy.home> (raw)
Hi,
I've done some tests with the patch I've just posted,
and results are encouraging indeed.
I managed to do 18 (!) diffs on /usr/src/linux without
much trouble. During that period, all kinds of memory
maps from other programs were paged out and things
kinda thrashed, but WorkMan was able to update it's
slidebars at least once every 2 seconds and even Netscape
(version 3) was usable, as long as you kept moving the
mouse :-)
Maybe it's time for implementing minimum RSS limits
for processes, but this needs to go hand in hand with
process suspension and other things...
Rik.
+-------------------------------------------+--------------------------+
| Linux: - LinuxHQ MM-patches page | Scouting webmaster |
| - kswapd ask-him & complain-to guy | Vries cubscout leader |
| http://www.fys.ruu.nl/~riel/ | <H.H.vanRiel@fys.ruu.nl> |
+-------------------------------------------+--------------------------+
reply other threads:[~1998-03-12 17:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.3.91.980312173402.664A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.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