public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tommy Reynolds <Tommy.Reynolds@MegaCoder.com>
To: DervishD <lkml@dervishd.net>
Cc: mailinglists@unix-scripts.com, linux-kernel@vger.kernel.org
Subject: Re: Memory, where's it going?
Date: Wed, 28 Dec 2005 08:00:21 -0600	[thread overview]
Message-ID: <20051228080021.44263f03.Tommy.Reynolds@MegaCoder.com> (raw)
In-Reply-To: <20051228095512.GA25654@DervishD>

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

Uttered DervishD <lkml@dervishd.net>, spake thus:

> > I understand the concept and why things are cached, i've just never
> > seen it cache this much before..
> Swap memory is not used just when the machine has no free memory.
> Although this is a rough explanation and doesn't describe exactly the
> swap mechanism, some apps will remain into swap space even if there's
> plenty of free RAM available, as long as they are not used. 

Yes.  Let me amplify that..

It is not apps that are being evicted from main memory, only some
of their pages.  The kernel will do "anticipatory swapping", moving
pages that have not be used for some time out to the paging store, to
make room just in case it might be needed for a burst of activity in
the future.  This is a very neat feature.

As you pointed out, do not get excited about having no free memory:
the kernel is just doing its job especially well.

However, DO get excited if swap space gets short or you see frequent
page-in activity.

Cheers

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-12-28 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28  8:45 Memory, where's it going? Shaun
2005-12-28  8:53 ` DervishD
2005-12-28  9:06   ` Shaun
2005-12-28  9:55     ` DervishD
2005-12-28 14:00       ` Tommy Reynolds [this message]
2005-12-28 16:41         ` DervishD

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=20051228080021.44263f03.Tommy.Reynolds@MegaCoder.com \
    --to=tommy.reynolds@megacoder.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@dervishd.net \
    --cc=mailinglists@unix-scripts.com \
    /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