![]() | ||||||||||
Messages in this thread |
Andrew Morton wrote: > shrink_slab-for-all-zones.patch > vm: scan slab in response to highmem scanning > > zone-balancing-fix.patch > vmscan: zone balancing fix On 2.6.3 + [1] + nfsd-lofft.patch running on a 1GB ram file server. I have noticed two related issues. First, under 2.6.3 it averages about 90MB[2] anon memory, and 30MB with the -mm4 vm (the rest is in swap cache). This could balance out on the normal non-idle week-day load though... Second the -mm4 vm, there is a lot more swapping[3] going on during the daily updatedb, and backup runs that are performed on this machine. I'd have to call this second issue a regression, but I want to run it a couple more days to see if it gets any better (unless you agree of course). Mike [1] instrument-highmem-page-reclaim.patch blk_congestion_wait-return-remaining.patch vmscan-remove-priority.patch kswapd-throttling-fixes.patch vm-dont-rotate-active-list.patch vm-lru-info.patch vm-shrink-zone.patch vm-tune-throttle.patch shrink_slab-for-all-zones.patch zone-balancing-fix.patch zone-balancing-batching.patch [2] http://www.matchmail.com/stats/lrrd/matchmail.com/fileserver.matchmail.com-memory.html [3] http://www.matchmail.com/stats/lrrd/matchmail.com/fileserver.matchmail.com-swap.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-03-22 13:01 [from the cache] ©2003-2008 | ||||||||||