From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ron Maeder <rlm@orionmulti.com>
Cc: riel@surriel.com, akpm@osdl.org, linux-mm@kvack.org
Subject: Re: mmap() > phys mem problem
Date: Wed, 16 Jun 2004 13:08:10 +1000 [thread overview]
Message-ID: <40CFB99A.8080508@yahoo.com.au> (raw)
In-Reply-To: <40CE6ADE.4040903@yahoo.com.au>
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: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-06-16 3:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 22:04 Ron Maeder
2004-06-15 3:19 ` Nick Piggin
2004-06-16 3:08 ` Nick Piggin [this message]
2004-06-16 6:37 ` Ron Maeder
-- strict thread matches above, loose matches on Subject: below --
2004-05-25 22:40 Ron Maeder
2004-05-29 2:08 ` Rik van Riel
2004-05-30 4:47 ` Ron Maeder
2004-05-30 9:24 ` Nick Piggin
2004-05-30 10:15 ` Andrew Morton
2004-06-05 19:21 ` Ron Maeder
2004-06-06 1:55 ` Nick Piggin
2004-06-06 23:51 ` Rik van Riel
2004-06-07 3:59 ` Nick Piggin
2004-06-07 12:04 ` Rik van Riel
2004-06-08 0:03 ` Nick Piggin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40CFB99A.8080508@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=rlm@orionmulti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox