From: "Matthew D. Pitts" <mpitts@suite224.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.19-pre3-ac1
Date: Sun, 17 Mar 2002 18:52:51 -0500 [thread overview]
Message-ID: <003901c1ce0e$e5c15040$b0d3fea9@pcs686> (raw)
In-Reply-To: <20020316190415.38CE14E534@mail.vnsecurity.net> <E16mLFj-000794-00@the-village.bc.nu> <20020317053624.GD23938@matchmail.com>
L-K developers,
What is the recomended amount of swap if you have a PC with 384 MB ram?
Matthew
----- Original Message -----
From: Mike Fedyk <mfedyk@matchmail.com>
To: <MrChuoi@yahoo.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Sunday, March 17, 2002 12:36 AM
Subject: Re: Linux 2.4.19-pre3-ac1
> On Sat, Mar 16, 2002 at 08:58:11PM +0000, Alan Cox wrote:
> > > SwapTotal: 65528 kB
> > > SwapFree: 65528 kB
> > > Committed_AS: 57252 kB
> >
> > Ok at this point you have 64Mb of free swap, and at worse (absolutely
worst
> > pure theory) have 57Mb committed
> >
> > > LowTotal: 126856 kB
> > > SwapTotal: 65528 kB
> > > SwapFree: 63324 kB
> > > Committed_AS: 226160 kB
> >
> > So you have 128Mb of RAM, 64Mb of swap, and if all pages are touched you
> > would need 226Mb of swap + ram (minus kernel overhead). Looks like the
> > machine is hovering on the edge
> >
>
> In Other Words (IOW), add more swap like everyone else said.
>
> The rmap design does use a bit more memory (about 400k for 128MB ram) for
> the reverse mapping tables, so that could push you over into an OOM case.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-03-17 23:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 1:42 Linux 2.4.19-pre3-ac1 Alan Cox
2002-03-16 2:44 ` Mike Fedyk
2002-03-16 5:33 ` MrChuoi
2002-03-16 6:00 ` J Sloan
2002-03-16 7:52 ` MrChuoi
2002-03-16 17:30 ` Alan Cox
2002-03-16 17:50 ` MrChuoi
2002-03-16 18:00 ` Alan Cox
2002-03-16 19:14 ` MrChuoi
2002-03-16 20:58 ` Alan Cox
2002-03-17 5:36 ` Mike Fedyk
2002-03-17 23:52 ` Matthew D. Pitts [this message]
2002-03-18 0:01 ` Mike Fedyk
2002-03-18 3:02 ` MrChuoi
2002-03-18 3:01 ` Mike Fedyk
2002-03-18 3:03 ` Rik van Riel
2002-03-19 1:46 ` MrChuoi
2002-03-18 11:44 ` Alan Cox
2002-03-18 21:23 ` toon
2002-03-19 1:39 ` MrChuoi
2002-03-19 1:55 ` Alan Cox
2002-03-19 5:54 ` Zwane Mwaikambo
2002-03-19 6:20 ` Mike Fedyk
2002-03-19 6:46 ` Zwane Mwaikambo
2002-03-19 13:32 ` Alan Cox
2002-03-19 18:04 ` Mike Fedyk
2002-03-19 18:26 ` Alan Cox
2002-03-19 18:29 ` Mike Fedyk
2002-03-21 5:11 ` Mike Fedyk
2002-03-21 13:32 ` Alan Cox
2002-03-18 5:24 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2002-03-17 13:55 jarmo kettunen
2002-03-17 17:23 ` 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='003901c1ce0e$e5c15040$b0d3fea9@pcs686' \
--to=mpitts@suite224.net \
--cc=linux-kernel@vger.kernel.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