Following this email are five patches which represent the current state of the lumpy reclaim patches; collectivly lumpy v4. This patch kit is designed as a complete drop-in replacement for the lumpy patches in 2.6.20-mm2. This stack is split out to show the incremental changes in this version. Andrew please replace your current lumpy stack with this one, you may prefer to fold this kit into a single patch lumpy-v4.
Comparitive testing between lumpy-v3 and lump-v4 generally shows a small improvement, coming from the improved matching of pages taken from the end of the active/inactive list (patch 2 in this series). I have taken the lumpy-v2 patches and fixes as found in 2.6.20-rc6-mm2 and folded them back into a single patch (collectivly lumpy v3), updating attribution. On top of this are are four patches which represent the updates mainly coming from the detailed review comments from Andrew Morton: lumpy-reclaim-v3: folded back base, lumpy-v3, lumpy-isolate_lru_pages-wants-to-specifically-take-active-or-inactive-pages: ensure we take pages of the expected type from the end of the active/ inactive lists. This is both a performance and correctness fix, lumpy-ensure-that-we-compare-PageActive-and-active-safely: ensure comparisons between PageActive() and coded booleans are safe should PageActive() not return 1/0, lumpy-update-commentry-on-subtle-comparisons-and-rounding-assumptions: update the code commentary to explain the subtle exit conditions, and lumpy-only-check-for-valid-pages-when-holes-are-present: remove expensive check for invalid pages within MAX_ORDER blocks where those cannot exist. Against: 2.6.20-mm2 -apw - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
