|| ||Matthew Dobson <firstname.lastname@example.org>|
|| ||[RFC][PATCH 0/6] Critical Page Pool|
|| ||Tue, 13 Dec 2005 23:50:34 -0800|
|| ||email@example.com, Sridhar Samudrala <firstname.lastname@example.org>, email@example.com,
Andrew Morton <firstname.lastname@example.org>,
Linux Memory Management <email@example.com>|
Here is the latest version of the Critical Page Pool patches. Besides
bugfixes, I've removed all the slab cleanup work from the series. Also,
since one of the main questions about the patch series seems to revolve
around how to appropriately size the pool, I've added some basic statistics
about the critical page pool, viewable by reading
/proc/sys/vm/critical_pages. The code now exports how many pages were
requested, how many pages are currently in use, and the maximum number of
pages that were ever in use.
The overall purpose of this patch series is to all a system administrator
to reserve a number of pages in a 'critical pool' that is set aside for
situations when the system is 'in emergency'. It is up to the individual
administrator to determine when his/her system is 'in emergency'. This is
not meant to (necessarily) anticipate OOM situations, though that is
certainly one possible use. The purpose this was originally designed for
is to allow the networking code to keep functioning despite the sytem
losing its (potentially networked) swap device, and thus temporarily
putting the system under exreme memory pressure.
Any comments about the code or the overall design are very welcome.
Patches agaist 2.6.15-rc5.