|| ||Peter Zijlstra <firstname.lastname@example.org>|
|| ||email@example.com, firstname.lastname@example.org,
|| ||[PATCH 0/9] VM deadlock avoidance -v10|
|| ||Tue, 16 Jan 2007 10:45:57 +0100|
|| ||David Miller <email@example.com>,
Peter Zijlstra <firstname.lastname@example.org>|
These patches implement the basic infrastructure to allow swap over networked
The basic idea is to reserve some memory up front to use when regular memory
To bound network behaviour we accept only a limited number of concurrent
packets and drop those packets that are not aimed at the connection(s) servicing
the VM. Also all network paths that interact with userspace are to be avoided -
e.g. taps and NF_QUEUE.
PF_MEMALLOC is set when processing emergency skbs. This makes sense in that we
are indeed working on behalf of the swapper/VM. This allows us to use the
regular memory allocators for processing but requires that said processing have
bounded memory usage and has that accounted in the reserve.
I am particularly looking for comments on the design; is this acceptable?
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html