public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Rene Rebe <rene.rebe@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc1 VM swaps out too much
Date: Mon, 5 May 2003 19:53:56 -0700	[thread overview]
Message-ID: <20030506025356.GD8350@matchmail.com> (raw)
In-Reply-To: <20030505.204036.596526358.rene.rebe@gmx.net>

On Mon, May 05, 2003 at 08:40:36PM +0200, Rene Rebe wrote:
> Hi,
> 
> 2.5.68 is much smoother, quite less swap is used, my editors are not
> pulled out of the swap all the time:
> 
> $ free
>              total       used       free     shared    buffers     cached
> Mem:        515848     505804      10044          0      92808     173876
> -/+ buffers/cache:     239120     276728
> Swap:       524624      35612     489012

You will notice that -aa is better and -rmap is even better still.

I can run badblocks on two drives without very much swapping on 192MB with
-rmap15[aeg]

      reply	other threads:[~2003-05-06  2:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-03 19:55 2.4.21-rc1 VM swaps out too much Rene Rebe
2003-05-05 18:40 ` Rene Rebe
2003-05-06  2:53   ` Mike Fedyk [this message]

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=20030506025356.GD8350@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.rebe@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox