From: Jonathan Morton <chromi@cyberspace.org>
To: Maciej Zenczykowski <maze@druid.if.uj.edu.pl>,
<linux-kernel@vger.kernel.org>
Subject: Re: Thrashing WITHOUT swap.
Date: Sun, 24 Jun 2001 21:07:55 +0100 [thread overview]
Message-ID: <a05101000b75bf87731b8@[192.168.239.105]> (raw)
In-Reply-To: <Pine.LNX.4.33.0106242133550.19801-100000@druid.if.uj.edu.pl>
In-Reply-To: <Pine.LNX.4.33.0106242133550.19801-100000@druid.if.uj.edu.pl>
>Now my question is how can it be
>thrashing with swap explicitly turned off?
Easy. All applications are themselves swap space - the binary is
merely memory-mapped onto the executable file. When the system gets
low on memory, the only thing it can do is purge some binary pages,
and then repeatedly page them back in from the original executable
file.
If you added a little bit of swap, it would be able to page out some
idle data rather than binaries, and would probably avoid thrashing.
--
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: chromi@cyberspace.org (not for attachments)
website: http://www.chromatix.uklinux.net/vnc/
geekcode: GCS$/E dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$
V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
tagline: The key to knowledge is not to rely on people to teach you it.
next prev parent reply other threads:[~2001-06-24 20:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9h7ne1$1bn$1@ns1.clouddancer.com>
2001-06-24 19:47 ` Maciej Zenczykowski
2001-06-24 20:07 ` Jonathan Morton [this message]
2001-06-24 21:36 ` Alan Cox
2001-06-25 8:13 ` Xavier Bestel
2001-06-25 16:14 ` Mike Galbraith
2001-06-25 9:21 ` Helge Hafting
2001-06-25 16:02 ` [OT] " Daniel Phillips
2001-06-25 16:16 ` Colonel
2001-06-25 16:32 ` Daniel Phillips
2001-06-26 12:36 ` john slee
2001-06-27 12:52 ` Ookhoi
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='a05101000b75bf87731b8@[192.168.239.105]' \
--to=chromi@cyberspace.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maze@druid.if.uj.edu.pl \
/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®