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, 19 Jun 1998 09:33:54 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.980619093210.6052C-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <19980618235448.18503@adore.lightlink.com>
[CC-ed to linux-mm, and it should stay that way...]
On Thu, 18 Jun 1998, Paul Kimoto wrote:
> For completeness, here is the fragmentation report for each:
> > Jun 18 01:24:48 ( 48*4kB 7*8kB 1*16kB 1*32kB 4*64kB 1*128kB = 680kB)
> > Jun 18 18:03:53 ( 1*4kB 28*8kB 39*16kB 2*32kB 1*64kB 1*128kB = 1108kB)
Damn, this looks near-perfect for normal system load...
I really don't understand what's wrong.
> If you have other suggestions for things to try, with the reduction in
> memory (from 48 MB) the problems seem to arise in about half the time.
I wonder what kind of software / networking app you are using,
and what memory usage those programs have...
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-19 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19980618235448.18503@adore.lightlink.com>
1998-06-19 7:33 ` Rik van Riel [this message]
1998-06-19 15:01 ` update re: fork() failures [in 2.1.103] Paul Kimoto
1998-06-19 16:59 ` Rik van Riel
1998-06-19 20:14 ` Paul Kimoto
1998-06-20 0:48 ` George Woltman
1998-06-21 20:19 ` update re: fork() failures in 2.1.103 Paul Kimoto
[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
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.96.980619093210.6052C-100000@mirkwood.dummy.home \
--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