All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Pritchard <steve@silug.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [uml-user] Network lags
Date: Sat, 10 Apr 2004 11:46:19 -0500	[thread overview]
Message-ID: <20040410164619.GA12830@osiris.silug.org> (raw)
In-Reply-To: <20040410151220.GB1297@vernix.org>

On Sat, Apr 10, 2004 at 11:12:20AM -0400, Nicholas E. Walker wrote:
> However, this is sort of a misguided idea.  If you have enough memory,
> nothing will get swapped unless something in memory is so unused that it
> would be more efficient to swap it out and use the memory for cache.

That behavior seems to be very dependent on the kernel you are
running.  For example, a Red Hat 2.4.20 kernel seems to really, really
want to swap:

             total       used       free     shared    buffers     cached
Mem:       2064704    2053224      11480          0       9432    1212940
-/+ buffers/cache:     830852    1233852
Swap:      4176892    1597508    2579384

I would expect that system to be swapping, but not *nearly* that much.

Steve
-- 
Steven Pritchard - K&S Pritchard Enterprises, Inc.
Email: steve@kspei.com             http://www.kspei.com/
Phone: (618)398-7360               Mobile: (618)567-7320


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-04-10 16:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.59.9.0404091209570.10714@hathi.bw-networx.net>
     [not found] ` <185d01c41e23$5996cc00$2000000a@schlepptopp>
2004-04-09 12:47   ` [uml-devel] Re: [uml-user] Network lags roland
2004-04-09 16:26     ` Jeff Dike
2004-04-09 18:33       ` [uml-devel] uml responsivenes or "AS vs DEADLINE Scheduler on uml-host" - was: " roland
2004-04-10 12:28         ` BlaisorBlade
2004-04-13 21:26           ` roland
2004-04-14  1:02             ` Henrik Nordstrom
     [not found]       ` <c58kbu$el1$1@sea.gmane.org>
2004-04-10 14:08         ` [uml-devel] " Jeff Dike
2004-04-10 14:00           ` Sven Köhler
2004-04-10 17:07             ` Jeff Dike
2004-04-10 21:22               ` Sven Köhler
2004-04-10 23:29                 ` Henrik Nordstrom
2004-04-11  3:45                 ` attriel
2004-04-15  0:31               ` roland
2004-04-15 12:01                 ` David Cannings
     [not found]                   ` <407EADE0.8010308@cox.net>
2004-04-15 21:11                     ` roland
2004-04-16 15:12                   ` Matthew Bloch
2004-04-18 10:54                     ` roland
2004-04-10 14:50           ` [uml-devel] Re: V=R Michael Koehne
2004-04-11 16:54             ` BlaisorBlade
2004-04-11 17:17             ` Nicholas E. Walker
2004-04-10 15:12           ` [uml-devel] Re: [uml-user] Network lags Nicholas E. Walker
2004-04-10 16:46             ` Steven Pritchard [this message]
2004-04-10 23:41               ` Henrik Nordstrom

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=20040410164619.GA12830@osiris.silug.org \
    --to=steve@silug.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.