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 10:51:32 +1100	[thread overview]
Message-ID: <404FAA04.1020300@cyberone.com.au> (raw)
In-Reply-To: <404F651B.1030202@matchmail.com>



Mike Fedyk wrote:

> Nick Piggin wrote:
>
>>
>>
>> Mike Fedyk wrote:
>>
>>> Andrew Morton wrote:
>>>
>>>> Mike Fedyk <mfedyk@matchmail.com> wrote:
>>>>
>>>>> 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.
>>>
>>>
>>>
>>>
>>> Andrew, it looks like you're right.  This[1] server doesn't seem to 
>>> be hitting swap enough.  But my other[2] file server is doing great 
>>> with it on the other hand (though, it hasn't swapped at all).
>>>
>>
>> Just curious, what makes you say [1] isn't hitting swap enough and [2]
>> is OK? The graphs are better now, by the way. Thank you.
>
>
> Well, with [1], I know most of those apps aren't being used, so I'm 
> sure it should be hitting swap more.
>
> And with [2], it isn't fair since I'm just happy it's not swapping 
> throughout the day and all of userspace is in ram, but it's probably 
> not good either.  And I'm sure there are some gettys and such that 
> aren't being used, so they should have swapped out by now.
>


Yep OK.


>>
>>> Maybe a little tuning is in order?
>>>
>>> Any patches I should try?
>>>
>>
>> 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.

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

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

> Do you have a patch against -mm (you wrote to ask for your latest...)?
>

Yep...


  reply	other threads:[~2004-03-10 23:53 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 [this message]
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=404FAA04.1020300@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