public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: VM patches in 2.6.4-rc1-mm2
Date: Thu, 11 Mar 2004 11:25:03 +1100	[thread overview]
Message-ID: <404FB1DF.3070605@cyberone.com.au> (raw)
In-Reply-To: <404FAFFE.9010403@matchmail.com>



Mike Fedyk wrote:

> 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?
>

There have been no VM patches merged into mainline. I just mean that
neither mm or mainline does any mapped memory scanning when memory
pressure is low.

>>
>> 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.
>


For the one that is swapping, yes this would be happening.


>>
>> 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
>


Well all the ones in -mm now are probably right to go to 2.6.5
I hope.


  reply	other threads:[~2004-03-11  0:25 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
2004-03-11  0:25               ` Nick Piggin [this message]
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=404FB1DF.3070605@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    /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