linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Vier <tmv5@home.com>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.5-ac17
Date: Fri, 22 Jun 2001 18:40:40 -0400	[thread overview]
Message-ID: <20010622184040.A765@zero> (raw)
In-Reply-To: <20010621222557.A553@zero> <Pine.LNX.4.33.0106220722450.535-100000@mikeg.weiden.de>
In-Reply-To: <Pine.LNX.4.33.0106220722450.535-100000@mikeg.weiden.de>; from mikeg@wen-online.de on Fri, Jun 22, 2001 at 09:06:42AM +0200

On Fri, Jun 22, 2001 at 09:06:42AM +0200, Mike Galbraith wrote:
> It's not actually swapping unless you see IO (si/so).  It's allocating
> swap space, but won't send pages out to disk unless there's demand. One

if it's pre-allocation, why does it show up as "used"? "reserved" would be a
better fit.

> benefit of this early allocation is that idle pages will be identified
> prior to demand, and will be moved out of the way sooner.  Watch as

how long can swap allocation possibly take? certainly no where near as long
as a write to disk takes. my box has a half gig of ram, pre-allocation is a
waste of cpu. i never hit swap.

> memory demand rises, and you should see these pages migrating to disk
> and staying there.. buys you more working space.

-- 
Tom Vier <tmv5@home.com>
DSA Key id 0x27371A2C

  reply	other threads:[~2001-06-22 22:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 16:38 Linux 2.4.5-ac17 Alan Cox
2001-06-21 17:04 ` Rik van Riel
2001-06-21 17:47 ` Craig Schlenter
2001-06-21 18:06   ` Alan Cox
2001-06-21 20:08   ` Gary White (Network Administrator)
2001-06-21 19:51 ` Tom Vier
2001-06-21 21:11   ` Alan Cox
2001-06-22  2:25 ` Tom Vier
2001-06-22  7:06   ` Mike Galbraith
2001-06-22 22:40     ` Tom Vier [this message]
2001-06-22 22:06       ` Marcelo Tosatti
2001-06-23  3:46       ` Mike Galbraith

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=20010622184040.A765@zero \
    --to=tmv5@home.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    /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;
as well as URLs for NNTP newsgroup(s).