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.103]
Date: Fri, 19 Jun 1998 18:59:56 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.980619185625.6318F-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <19980619110148.53909@adore.lightlink.com>
On Fri, 19 Jun 1998, Paul Kimoto wrote:
> On Fri, Jun 19, 1998 at 09:33:54AM +0200, Rik van Riel wrote:
> > I wonder what kind of software / networking app you are using,
> > and what memory usage those programs have...
>
> It's a mixed libc5/libc6 system.
> Here is a snapshot of the Top 20 in RSS:
>
> %CPU %MEM SIZE RSS
> 1.3 18.9 13552 5876 Xwrapper XFree 3.3.2.2
> 1.0 18.4 10612 5716 netscape 3.01
> 95.7 1.6 9364 520 mprime 15.4.2 (internet Mersenne prime search)
Shouldn't be much of a problem... But 'eh, does the
Mersenne program regularly do memory I/O?
It could be that it loads large chunks of memory and
frees small portions from the middle of it. The Linux
MM system could have a problem with that...
Of course we should be able to handle such stuff, but
with the current buddy allocator things might just get
a little bit tricky :(
The reason I picked this process, is that it's RSS is
only one 18th of it's total size, which is somewhat
weird for a 'normal' Unix process.
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
next prev parent reply other threads:[~1998-06-19 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19980618235448.18503@adore.lightlink.com>
1998-06-19 7:33 ` update re: fork() failures in 2.1.101 Rik van Riel
1998-06-19 15:01 ` update re: fork() failures [in 2.1.103] Paul Kimoto
1998-06-19 16:59 ` Rik van Riel [this message]
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
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.980619185625.6318F-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