From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-nfs-owner@vger.kernel.org Received: from mx1.redhat.com ([209.132.183.28]:19974 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752654Ab2FTPXz (ORCPT ); Wed, 20 Jun 2012 11:23:55 -0400 Message-ID: <4FE1EABB.5060105@redhat.com> Date: Wed, 20 Jun 2012 11:22:35 -0400 From: Rik van Riel MIME-Version: 1.0 To: Mel Gorman CC: Andrew Morton , Linux-MM , Linux-Netdev , Linux-NFS , LKML , David Miller , Trond Myklebust , Neil Brown , Christoph Hellwig , Peter Zijlstra , Mike Christie , Eric B Munson Subject: Re: [PATCH 01/12] netvm: Prevent a stream-specific deadlock References: <1340185081-22525-1-git-send-email-mgorman@suse.de> <1340185081-22525-2-git-send-email-mgorman@suse.de> In-Reply-To: <1340185081-22525-2-git-send-email-mgorman@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: linux-nfs-owner@vger.kernel.org List-ID: 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 > Signed-off-by: Mel Gorman > Acked-by: David S. Miller Acked-by: Rik van Riel