From: christophe barbe <christophe.barbe@lineo.fr>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "Mike A . Harris" <mharris@opensourceadvocate.org>,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Is swap == 2 * RAM a permanent thing?
Date: Thu, 15 Mar 2001 17:09:10 +0100 [thread overview]
Message-ID: <20010315170910.C4921@pc8.inup.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0103150720100.757-100000@asdf.capslock.lan> <Pine.LNX.4.21.0103151005210.4165-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.21.0103151005210.4165-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on jeu, mar 15, 2001 at 14:08:50 +0100
Please Rik, could you explain what you mean with "reclaim swap space when we run out".
In my (limited) understanding, when there's no more free memory (ram and swap space), the kernel starts to kill process (and the choice is a difficult point).
Are you proposing to add an API to reclaim swap instead of killing process ?
Other thing (certainly related) what is supposed to have changed between 2.2 and 2.4.
Thanks,
Christophe
On jeu, 15 mar 2001 14:08:50 Rik van Riel wrote:
> On Thu, 15 Mar 2001, Mike A. Harris wrote:
>
> > Is the fact that we're supposed to use double the RAM size as
> > swap a permanent thing or a temporary annoyance that will get
> > tweaked/fixed in the future at some point during 2.4.x perhaps?
> >
> > What are the technical reasons behind this change?
>
> The reason is that the Linux 2.4 kernel no longer reclaims swap
> space on swapin (2.2 reclaimed swap space on write access, which
> lead to fragmented swap space in lots of workloads).
>
> This means that a lot of memory ends up "duplicated" in RAM and
> in swap.
>
> I plan on doing some code to reclaim swap space when we run out,
> but Linus doesn't seem to like that idea very much. His argument
> (when you're OOM, you should just fail instead of limp along)
> makes a lot of sense, however, and the reclaiming of swap space
> isn't really high on my TODO list ...
>
> OTOH, for people who have swap < RAM and use it just as a small
> overflow area, Linus' argument falls short, so I guess some time
> in the future we will have code to reclaim swap space when needed.
>
> regards,
>
> Rik
> --
> Virtual memory is like a game you can't win;
> However, without VM there's truly nothing to lose...
>
> http://www.surriel.com/
> http://www.conectiva.com/ http://distro.conectiva.com.br/
>
> -
> 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/
>
--
Christophe Barbé
Software Engineer
Lineo High Availability Group
42-46, rue Médéric
92110 Clichy - France
phone (33).1.41.40.02.12
fax (33).1.41.40.02.01
www.lineo.com
next prev parent reply other threads:[~2001-03-15 16:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 12:28 Is swap == 2 * RAM a permanent thing? Mike A. Harris
2001-03-15 13:08 ` Rik van Riel
2001-03-15 14:24 ` Mike Harrold
2001-03-16 0:47 ` Rik van Riel
2001-03-15 16:09 ` christophe barbe [this message]
2001-03-15 23:26 ` Rik van Riel
2001-03-15 17:20 ` christophe barbe
2001-03-15 17:43 ` James Lewis Nance
2001-03-16 1:25 ` Rik van Riel
2001-03-16 2:52 ` kernel benchmark gis88530
2001-03-15 15:23 ` Is swap == 2 * RAM a permanent thing? Ketil Froyn
-- strict thread matches above, loose matches on Subject: below --
2001-03-15 17:19 Torrey Hoffman
2001-03-15 19:22 ` William T Wilson
2001-03-16 2:44 ` Rik van Riel
2001-03-15 20:11 ` LA Walsh
2001-03-16 3:56 ` Rik van Riel
2001-03-15 21:45 ` Andrzej Krzysztofowicz
2001-03-16 5:08 ` Rik van Riel
2001-03-19 15:21 ` Guennadi Liakhovetski
2001-03-17 17:59 ` Boris Pisarcik
2001-03-17 17:53 ` Alexander Viro
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=20010315170910.C4921@pc8.inup.com \
--to=christophe.barbe@lineo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mharris@opensourceadvocate.org \
--cc=riel@conectiva.com.br \
/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