From: Rik van Riel <riel@conectiva.com.br>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: Linux responsiveness under heavy load
Date: Wed, 8 Mar 2000 19:26:22 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0003081920500.4639-100000@duckman.conectiva> (raw)
In-Reply-To: <20000308223851.A9519@pcep-jamie.cern.ch>
On Wed, 8 Mar 2000, Jamie Lokier wrote:
[snip awful performance under load]
> A larger boost to keep-the-page-in-memory priority for pages
> referenced by "interactive" processes might be in order.
> Either faster vmscanning simply a higher priority for pages
> found to be used. Might not be too hard to implement either.
Indeed it shouldn't be. Having a two-phase NRU unmapping in the
page table scanning and a maybe better LRU reclamation in
shrink_mmap() may help here, but the CPU cost may put some
people off...
Then again, not having this better memory reclamation is probably
more expensive than having it :)
Now where did I put that asbestos underwear?
> A larger priority for page-in I/O due to interactive process too
> might help too. Some modification of Andrea's elevator. But
> that doesn't seem so easy.
Read requests are easily tied to a process, so this could
be relatively easy. Doing it properly before 2.5 may be a
little difficult though ...
regards,
Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.
http://www.conectiva.com/ http://www.surriel.com/
--
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 parent reply other threads:[~2000-03-08 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000308223851.A9519@pcep-jamie.cern.ch>
2000-03-08 22:26 ` Rik van Riel [this message]
2000-03-08 22:39 ` Jamie Lokier
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.0003081920500.4639-100000@duckman.conectiva \
--to=riel@conectiva.com.br \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=lk@tantalophile.demon.co.uk \
--cc=riel@nl.linux.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