Messages in this thread | | | Date | Wed, 20 Jun 2012 11:22:35 -0400 | From | Rik van Riel <> | Subject | Re: [PATCH 01/12] netvm: Prevent a stream-specific deadlock |
| |
On 06/20/2012 05:37 AM, Mel Gorman wrote: > It could happen that all !SOCK_MEMALLOC sockets have buffered so > much data that we're over the global rmem limit. This will prevent > SOCK_MEMALLOC buffers from receiving data, which will prevent userspace > from running, which is needed to reduce the buffered data. > > Fix this by exempting the SOCK_MEMALLOC sockets from the rmem limit. > Once this change it applied, it is important that sockets that set > SOCK_MEMALLOC do not clear the flag until the socket is being torn down. > If this happens, a warning is generated and the tokens reclaimed to > avoid accounting errors until the bug is fixed. > > [davem@davemloft.net: Warning about clearing SOCK_MEMALLOC] > Signed-off-by: Peter Zijlstra<a.p.zijlstra@chello.nl> > Signed-off-by: Mel Gorman<mgorman@suse.de> > Acked-by: David S. Miller<davem@davemloft.net>
Acked-by: Rik van Riel<riel@redhat.com>
| |