From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Paul Kimoto <kimoto@lightlink.com>
Cc: Linux MM <linux-mm@kvack.org>
Subject: Re: update re: fork() failures in 2.1.101
Date: Fri, 12 Jun 1998 06:36:53 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.3.95.980612063348.22741A-100000@localhost> (raw)
In-Reply-To: <19980611173940.51846@adore.lightlink.com>
[Paul get's "cannot fork" errors after 60 or more hours of
uptime. This suggests fragmentation problems.]
On Thu, 11 Jun 1998, Paul Kimoto wrote:
> > Hmm, the 'cannot fork' issue only starting after some
> > days of uptime... This suggests fragmentation. Is your
> > box very heavily loaded, or just lightly (VM-wise)?
>
> Light, I think; I have 48MB of RAM and usually end up with 8--16MB in swap.
> In normal operation I don't have to wait much for paging except for larger
> programs (netscape, xemacs, or big compilations).
Ahh, I think I see it now. The fragmentation on your system
persists because of the swap cache. The swap cache 'caches'
swap pages and kinda makes sure they are reloaded to the
same physical address.
Stephen, Ben: should we disable the swap cache when
fragmentation is high?
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
next parent reply other threads:[~1998-06-12 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19980611173940.51846@adore.lightlink.com>
1998-06-12 4:36 ` Rik van Riel [this message]
1998-06-12 22:58 ` Stephen C. Tweedie
[not found] <19980618235448.18503@adore.lightlink.com>
1998-06-19 7:33 ` 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.3.95.980612063348.22741A-100000@localhost \
--to=h.h.vanriel@phys.uu.nl \
--cc=kimoto@lightlink.com \
--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