Messages in this thread | | | From | alad@hss ... | Date | Mon, 31 Dec 2001 14:18:28 +0530 | Subject | max_mapped logic in shrink_cache() |
| |
Hi, we have in vmscan.c::shrink_cache() -- max_mapped = nr_pages << (9 - priority);
Here is the basic logic, in the time of high memory loads priority shall be less, consequently max_mapped shall be more. Thus in case of high memory pressure, instead of decreasing max_mapped we are increasing it, thus invoking out_of_memory() when we could easily have called swap_out().
what is the logic of increasing max_mapped when priority is decreased..
-- Amol
- 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/
| |