Christoph Lameter bc3e53f682 mm: distinguish between mlocked and pinned pages ... Some kernel components pin user space memory (infiniband and perf) (by increasing the page count) and account that memory as "mlocked". The difference between mlocking and pinning is: A. mlocked pages are marked with PG_mlocked and are exempt from swapping. Page migration may move them around though. They are kept on a special LRU list. B. Pinned pages cannot be moved because something needs to directly access physical memory. They may not be on any LRU list. I recently saw an mlockalled process where mm->locked_vm became bigger than the virtual size of the process (!) because some memory was accounted for twice: Once when the page was mlocked and once when the Infiniband layer increased the refcount because it needt to pin the RDMA memory. This patch introduces a separate counter for pinned pages and accounts them seperately. Signed-off-by: Christoph Lameter <cl@linux.com> Cc: Mike Marciniszyn <infinipath@qlogic.com> Cc: Roland Dreier <roland@kernel.org> Cc: Sean Hefty <sean.hefty@intel.com> Cc: Hugh Dickins <hughd@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2011-10-31 17:30:46 -07:00
..
core.c	mm: distinguish between mlocked and pinned pages	2011-10-31 17:30:46 -07:00
hw_breakpoint.c	perf: Add context field to perf_event	2011-07-01 11:06:38 +02:00
internal.h	perf: Remove the nmi parameter from the swevent and overflow interface	2011-07-01 11:06:35 +02:00
Makefile	perf: Split up buffer handling from core code	2011-06-09 12:57:54 +02:00
ring_buffer.c	perf: Remove the perf_output_begin(.sample) argument	2011-07-01 11:06:35 +02:00