From: Paul Kimoto <kimoto@lightlink.com>
To: Rik van Riel <H.H.vanRiel@phys.uu.nl>
Cc: Linux MM <linux-mm@kvack.org>, woltman@magicnet.net
Subject: Re: update re: fork() failures [in 2.1.103]
Date: Fri, 19 Jun 1998 16:14:17 -0400 [thread overview]
Message-ID: <19980619161417.40049@adore.lightlink.com> (raw)
In-Reply-To: <Pine.LNX.3.96.980619185625.6318F-100000@mirkwood.dummy.home>; from Rik van Riel on Fri, Jun 19, 1998 at 06:59:56PM +0200
On Fri, Jun 19, 1998 at 06:59:56PM +0200, Rik van Riel wrote:
>> %CPU %MEM SIZE RSS
>> 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...
> 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.
I *think* that it allocates a huge amount of memory,
then uses only a small portion of it.
The above shows an inconsistency between "ps" and "top":
according to "ps", SIZE=9364, RSS=404;
but according to "top", SIZE= 500, RSS=404, SWAP=96.
"grep '^Vm' /proc/<pid>/status" says
> VmSize: 9364 kB
> VmLck: 0 kB
> VmRSS: 464 kB
> VmData: 8400 kB
> VmStk: 12 kB
> VmExe: 72 kB
> VmLib: 580 kB
-Paul <kimoto@lightlink.com>
next prev parent reply other threads:[~1998-06-19 20:15 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
1998-06-19 20:14 ` Paul Kimoto [this message]
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=19980619161417.40049@adore.lightlink.com \
--to=kimoto@lightlink.com \
--cc=H.H.vanRiel@phys.uu.nl \
--cc=linux-mm@kvack.org \
--cc=woltman@magicnet.net \
/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