From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 15 Jun 2004 23:37:40 -0700 (PDT) From: Ron Maeder Subject: Re: mmap() > phys mem problem In-Reply-To: <40CFB99A.8080508@yahoo.com.au> Message-ID: References: <40CE6ADE.4040903@yahoo.com.au> <40CFB99A.8080508@yahoo.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: owner-linux-mm@kvack.org Return-Path: To: Nick Piggin Cc: riel@surriel.com, akpm@osdl.org, linux-mm@kvack.org List-ID: I can avoid this particular situation in the short term, but I can't avoid the general case in the long run. Thanks again. -Ron On Wed, 16 Jun 2004, Nick Piggin wrote: > Nick Piggin wrote: >> Ron Maeder wrote: >> >>> I tried upping /proc/sys/vm/min_free_kbytes to 4096 as suggested below, >>> with the same results (grinding to a halt, out of mem). >>> >>> Any other suggestions? Thanks for your help. >>> >> >> Hmm. Maybe ask linux-net and/or the NFS guys? >> >> You need to know the maximum amount of memory that your setup >> might need in order to write out one page. >> >> There might also be ways to reduce this, like reducing NFS >> transfer sizes or network buffers... I dunno. >> > > Actually no, I don't think that will help. I have an > idea that might help. Stay tuned :) > > For the time being, would it be at all possible to > work around it using your msync hack, turning swap on, > or doing read/write IO? > -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org