From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Jakob Østergaard" <jakob@unthought.net>
Cc: safemode <safemode@voicenet.com>,
"G. Hugh Song" <ghsong@kjist.ac.kr>,
linux-kernel@vger.kernel.org
Subject: Re: Plain 2.4.5 VM...
Date: Tue, 29 May 2001 00:38:45 -0400 [thread overview]
Message-ID: <3B1327D5.6484E61E@mandrakesoft.com> (raw)
In-Reply-To: <200105290232.f4T2W9m00876@bellini.kjist.ac.kr> <20010529061039.D29962@unthought.net> <01052900260800.29037@psuedomode>
> On Tuesday 29 May 2001 00:10, Jakob Østergaard wrote:
>
> > > > Mem: 381608K av, 248504K used, 133104K free, 0K shrd, 192K
> > > > buff
> > > > Swap: 255608K av, 255608K used, 0K free 215744K
> > > > cached
> > > >
> > > > Vanilla 2.4.5 VM.
>
> > It's not a bug. It's a feature. It only breaks systems that are run with
> > "too little" swap, and the only difference from 2.2 till now is, that the
> > definition of "too little" changed.
I am surprised as many people as this are missing,
* when you have an active process using ~300M of VM, in a ~380M machine,
2/3 of the machine's RAM should -not- be soaked up by cache
* when you have an active process using ~300M of VM, in a ~380M machine,
swap should not be full while there is 133M of RAM available.
The above quoted is top output, taken during the several minutes where
cc1plus process was ~300M in size. Similar numbers existed before and
after my cut-n-paste, so this was not transient behavior.
I can assure you, these are bugs not features :)
--
Jeff Garzik | Disbelief, that's why you fail.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-05-29 5:00 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 2:32 Plain 2.4.5 VM G. Hugh Song
2001-05-29 4:10 ` Jakob Østergaard
2001-05-29 4:26 ` safemode
2001-05-29 4:38 ` Jeff Garzik [this message]
2001-05-29 6:04 ` Mike Galbraith
2001-05-29 14:06 ` Gerhard Mack
2001-05-29 4:46 ` G. Hugh Song
2001-05-29 4:57 ` Jakob Østergaard
2001-05-29 7:13 ` Marcelo Tosatti
2001-05-29 9:10 ` Alan Cox
2001-05-29 15:37 ` elko
2001-05-29 20:09 ` Plain 2.4.5 VM... (and 2.4.5-ac3) Vincent Stemen
2001-05-29 20:16 ` Alan Cox
2001-05-29 21:36 ` Vincent Stemen
2001-05-30 6:02 ` Mike Galbraith
2001-05-30 19:58 ` Vincent Stemen
2001-05-30 20:11 ` Alan Cox
2001-05-30 20:17 ` Mike Galbraith
2001-05-31 3:47 ` Vincent Stemen
2001-05-31 6:18 ` Mike Galbraith
2001-05-30 20:30 ` Rik van Riel
2001-05-31 3:11 ` Vincent Stemen
[not found] ` <991254700.786.0.camel@tux.bitfreak.net>
2001-05-30 21:59 ` Vincent Stemen
2001-05-30 20:16 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-05-30 4:24 Plain 2.4.5 VM Craig Kulesa
2001-05-30 6:50 ` Mike Galbraith
2001-05-30 13:27 ` Jonathan Morton
2001-05-30 12:20 ` Marcelo Tosatti
2001-05-30 15:27 ` Mike Galbraith
2001-05-30 18:39 ` Rik van Riel
2001-05-30 17:19 ` Marcelo Tosatti
2001-05-30 20:33 ` Mike Galbraith
2001-05-30 19:25 ` Marcelo Tosatti
2001-05-31 5:20 ` Mike Galbraith
2001-05-30 15:18 ` Mike Galbraith
2001-05-30 19:16 ` Rik van Riel
2001-05-30 20:01 ` Mark Hahn
2001-05-30 20:35 ` Rik van Riel
2001-05-30 22:41 ` Jonathan Morton
2001-05-30 22:51 ` Marcelo Tosatti
[not found] <mailman.991098720.29883.linux-kernel2news@redhat.com>
2001-05-29 2:55 ` Pete Zaitcev
2001-05-29 0:32 Jeff Garzik
2001-05-29 1:13 ` Mohammad A. Haque
2001-05-29 1:14 ` Mohammad A. Haque
2001-05-29 8:51 ` Alan Cox
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=3B1327D5.6484E61E@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=ghsong@kjist.ac.kr \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@voicenet.com \
/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.