[lkml]   [2009]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 4/4] zone_reclaim_mode is always 0 by default
On Thu, 21 May 2009, KOSAKI Motohiro wrote:

> I can't catch up your message. Can you post your patch?
> Can you explain your sanity check?
> Now, I decide to remove "nr_online_nodes >= 4" condition.
> Apache regression is really non-sense.

Not sure what that means? Apache regresses with zone reclaim? My
measurements when we introduced zone reclaim showed just the opposite
because Apache would get node local memory and thus run faster. You can
screw this up of course if you load the system so high that the apache
processes are tossed around by the scheduler. Then the node local
allocation may be worse than round robin because all the pages allocated
by a process are now on one node if the scheduler moves the
process to a remote node then all accesses are penalized.

> > Even with 128 nodes and 256 cpus, I _NEVER_ see the
> > system swapping out before allocating off node so I can certainly not
> > reproduce the situation you are seeing.
> hmhm. but I don't think we can assume hpc workload.

System swapping due to zone reclaim? zone reclaim only reclaims unmapped
pages so it will not swap. Maybe some bug crept in in the recent changes?
Or you overrode the defaults for zone reclaim?

 \ /
  Last update: 2009-05-21 15:33    [W:0.099 / U:0.200 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site