From: Mike Fedyk <mfedyk@matchmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VM patches in 2.6.4-rc1-mm2
Date: Wed, 03 Mar 2004 19:57:49 -0800 [thread overview]
Message-ID: <4046A93D.9090305@matchmail.com> (raw)
In-Reply-To: <20040303193025.68a16dc4.akpm@osdl.org>
Andrew Morton wrote:
> Mike Fedyk <mfedyk@matchmail.com> wrote:
>
>>Andrew Morton wrote:
>>
>>>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.4-rc1/2.6.4-rc1-mm2/
>>>
>>>- More VM tweaks and tuneups
>>
>>Running 2.6.3-lofft-snsus-264rc1mm2vm (nfsd loff_t, sunrpc locking & -mm
>>VM patches). Seems to be working well.
>
>
> OK, good.
>
>
>>Most of the previous 2.6 kernels I was running on these servers would be
>>lightly hitting swap by now. This definitely looks better to me.
>
>
> It sounds worse to me. "Lightly hitting swap" is good. It gets rid of stuff,
> freeing up physical memory.
Swapping out is good to me. It's the swapping in, and out, and in,
and... that's bad.
>
> But I do not see a lot of difference here.
Let's let it run a few more days to make sure.
> The 900MB desktop machine is
> 300M into swap after 24 hours. That's usual.
Neither of my servers have 900MB ram...
Mike
next prev parent reply other threads:[~2004-03-04 3:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 4:15 2.6.4-rc1-mm2 Andrew Morton
2004-03-03 11:32 ` 2.6.4-rc1-mm2 J.A. Magallon
2004-03-03 18:46 ` 2.6.4-rc1-mm2 Adrian Bunk
2004-03-03 16:15 ` 2.6.4-rc1-mm2 (compile stats) John Cherry
2004-03-03 22:33 ` 2.6.4-rc1-mm2 Luiz Fernando Capitulino
2004-03-04 0:52 ` 2.6.4-rc1-mm2 Andrew Morton
2004-03-04 3:11 ` VM patches in 2.6.4-rc1-mm2 Mike Fedyk
2004-03-04 3:30 ` Andrew Morton
2004-03-04 3:57 ` Mike Fedyk [this message]
2004-03-10 8:20 ` Mike Fedyk
2004-03-10 8:36 ` Nick Piggin
2004-03-10 18:57 ` Mike Fedyk
2004-03-10 23:51 ` Nick Piggin
2004-03-11 0:17 ` Mike Fedyk
2004-03-11 0:25 ` Nick Piggin
2004-03-05 17:54 ` 2.6.4-rc1-mm[12] - dm_any_congested issues Valdis.Kletnieks
2004-03-06 3:09 ` Miquel van Smoorenburg
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=4046A93D.9090305@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@osdl.org \
--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