From: Mike Fedyk <mfedyk@matchmail.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: VM patches in 2.6.4-rc1-mm2
Date: Wed, 10 Mar 2004 16:17:02 -0800 [thread overview]
Message-ID: <404FAFFE.9010403@matchmail.com> (raw)
In-Reply-To: <404FAA04.1020300@cyberone.com.au>
Nick Piggin wrote:
>
>
> Mike Fedyk wrote:
>
>> Nick Piggin wrote:
>>> Mainline doesn't put enough pressure on slab with highmem systems. This
>>> creates a lot more ZONE_NORMAL pressure and that causes swapping.
>>>
>>
>> Yep, saw that. Especially with 128MB Highmem (eg, 1G RAM)
>>
>>> Now with the 2.6 VM, you don't do any mapped memory scaning at all
>>
>>
>>
>> You mean 2.6-mm?
>>
>
> Yes, either mm or linus.
>
Have there been any VM patches merged into mainline? Or are you saying
that the imbalance in mainline would be enough to overcome to lack of
scanning of mapped pages?
>>> while you only have a small amount of memory pressure. This means that
>>> truely inactive mapped pages never get reclaimed.
>>>
>>
>> If I have enough pressure, they will be eventually? But my caches
>> will still be smaller than optimal, right?
>>
>
> If you get a lot of pressure at one time it should push out your
> inactive mapped pages. Will get most of the really inactive ones,
> but it won't help pages becoming inactive in future.
>
Ok, I see. This might be happening, since it is steadily getting more
into swap.
>>> The patches you are using do not address this. My split active list
>>> patches should do so. Alternatively you can increase
>>> /proc/sys/vm/swappiness, but that isn't a complete solution, and might
>>> make things too swappy. It is a difficult beast to control.
>>
>>
>>
>> Has akpm said that he would be including the active split patch in -mm?
>>
>
> Hasn't looked at it much. Probably not until some of the more basic
> VM patches can get merged into -linus.
Yes, I wonder if the VM patches helped -mm in the reaim tests...
Let's get the fsfaz (free slab for all zones) into mainline asap! :-D
>> Do you have a patch against -mm (you wrote to ask for your latest...)?
>>
>
> Yep...
Let me get back to you sometime next week. So far, the VM is reacting
ok with this combined workload.
Mike
next prev parent reply other threads:[~2004-03-11 0:18 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
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 [this message]
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=404FAFFE.9010403@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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