From: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
To: Rik van Riel <H.H.vanRiel@phys.uu.nl>
Cc: Paul Kimoto <kimoto@lightlink.com>, Linux MM <linux-mm@kvack.org>
Subject: Re: update re: fork() failures in 2.1.101
Date: Fri, 12 Jun 1998 23:58:39 +0100 [thread overview]
Message-ID: <199806122258.XAA02298@dax.dcs.ed.ac.uk> (raw)
In-Reply-To: <Pine.LNX.3.95.980612063348.22741A-100000@localhost>
Hi,
On Fri, 12 Jun 1998 06:36:53 +0200 (MET DST), Rik van Riel
<H.H.vanRiel@phys.uu.nl> said:
> [Paul get's "cannot fork" errors after 60 or more hours of
> uptime. This suggests fragmentation problems.]
Kernel version?
> 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.
No. As it stands right now, the "caching" component of the swap cache
is an *on disk* cache of resident pages. Once the pages are swapped
out they are paged back in anywhere appropriate. That part of the
fragmentation does not persist.
The real problem is not swapper, I suspect, but the various consumers of
slab cache (especially dcache). The slab allocator has some really
nasty properties; just one single in-use object will pin an entire slab
(up to 32k) into memory. If the slabs become small, then it will be 4k
pages which get so pinned, and at that point we cannot allocate any
stack pages. There are a number of ways we may tackle this in 2.1, but
disabling the swap cache won't help at all.
--Stephen
next prev parent reply other threads:[~1998-06-12 23:13 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 ` update re: fork() failures in 2.1.101 Rik van Riel
1998-06-12 22:58 ` Stephen C. Tweedie [this message]
[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=199806122258.XAA02298@dax.dcs.ed.ac.uk \
--to=sct@dcs.ed.ac.uk \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.