mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Correctly determine amount of "free memory"
Date: Mon, 6 Dec 2004 10:26:20 -0800	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKKELNAEAB.davids@webmaster.com> (raw)
In-Reply-To: <06EF4EE36118C94BB3331391E2CDAAD9CD060A@exil1.paradigmgeo.net>


> Assuming that I define "free memory" as maximum memory that can be
> allocated without causing swapping, is there a way I can give the best
> "free memory" amount estimate?

	That's not really a meaningful question. In fact, technically, no matter
how much memory you allocate you won't change the amount of swapping because
allocation has no affect on the working set size.

> I've tried to play with /proc/meminfo values with some progress, but I'd
> like to get a qualified answer from people working with VM bits and
> bytes.

	The qualified answer is that /proc/meminfo gives you the available
information and what number you want depends upon what you plan to do with
it. Swapping is not necessarily the right metric for two reasons. First, a
system might swap even though it's under a perfectly normal (or even low)
load. Second, there are bad memory situations a system can get in even if
it's not swapping, for example, a system with no buffer cache for file I/O
wouldn't be swapping, but it wouldn't perform well either.

	DS



  parent reply	other threads:[~2004-12-06 18:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 14:53 Gregory Giguashvili
2004-12-06 15:16 ` bert hubert
2004-12-06 18:26 ` David Schwartz [this message]
2004-12-06 15:57 Gregory Giguashvili
2004-12-06 16:10 ` bert hubert
2004-12-06 17:04 Gregory Giguashvili
2004-12-06 19:00 Gregory Giguashvili
2004-12-07 15:58 Gregory Giguashvili

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=MDEHLPKNGKAHNMBLJOLKKELNAEAB.davids@webmaster.com \
    --to=davids@webmaster.com \
    --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®