mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jlnance@intrex.net
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x swap >= 2*memsize requirement status.
Date: Sat, 14 Jul 2001 11:23:04 -0400	[thread overview]
Message-ID: <20010714112304.B1327@bessie.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.21.0107141326001.12808-100000@polypc17.chem.rug.nl>
In-Reply-To: <Pine.LNX.4.21.0107141326001.12808-100000@polypc17.chem.rug.nl>; from jdejong@chem.rug.nl on Sat, Jul 14, 2001 at 01:42:46PM +0200

On Sat, Jul 14, 2001 at 01:42:46PM +0200, J.R. de Jong wrote:
> Can anyone shed some
> light on how 'required' this requirement really is and what one could
> expect to happen when this requirement is not met?

Well, I just swapoffed my swap partitions and I am still able to compose this
email, so I guess its not actually required.  I'm even building mozilla at
the same time.  Ill have to add the swap back before the mozilla build gets
to the final link stage :-)  I believe that the issue is that with 2.4 once
a process gets pages swapped out, it owns that area of swap until the process
dies.  The 2.2 kernel would free the swap space up when it swapped the
processes pages back into memory.  The 2.4 way performs much better than the
2.2 way.  The problem is that if the swap space is less than the ram size, it
is possible to fill up the swap and then strange things happen.  For example
consider a machine with 64M of ram and 64M of swap which is running 2 32M
processes.  Now lets say we start a third process that grows to a large value
and causes both of the original 32M processes to be swapped out.  Now the
third process dies a the two 32M process can run in memory again, but they
still own the swap space they were swapped into.  This means that when we
start a third process, it can not be swapped out since the swap space is
owned the the two original processes, they will get swapped out instead when
memory gets tight.

I know that people have worked on changing this behavior, but I do not know
what the current state of those changes is.

Hope this helps,

Jim

  reply	other threads:[~2001-07-14 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-14 11:42 J.R. de Jong
2001-07-14 15:23 ` jlnance [this message]
2001-07-14 14:27 Jonathan Brugge

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=20010714112304.B1327@bessie.localdomain \
    --to=jlnance@intrex.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

all inboxes | Powered by JetHome®