From: Ron Maeder <rlm@orionmulti.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Rik van Riel <riel@surriel.com>, linux-mm@kvack.org
Subject: Re: mmap() > phys mem problem
Date: Sat, 5 Jun 2004 12:21:35 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0406051219130.749@stimpy> (raw)
In-Reply-To: <40B9A855.3030102@yahoo.com.au>
Thanks very much for your response. I have had some help trying out the
patch and running recent versions of the kernel. The problem is not fixed
in 2.6.6+patch or in 2.6.7-rc2. Any other suggestions?
Ron
On Sun, 30 May 2004, Nick Piggin wrote:
> Ron Maeder wrote:
>> On Fri, 28 May 2004, Rik van Riel wrote:
>>
>>> On Tue, 25 May 2004, Ron Maeder wrote:
>>>
>>>> Is this an "undocumented feature" or is this a linux error? I would
>>>> expect pages of the mmap()'d file would get paged back to the original
>>>> file. I know this won't be fast, but the performance is not an issue
>>>> for
>>>> this application.
>>>
>>>
>>> It looks like a kernel bug. Can you reproduce this problem
>>> with the latest 2.6 kernel or is it still there ?
>>>
>>> Rik
>>
>>
>> I was able to reproduce the problem with the code that I posted on a 2.6.6
>> kernel.
>>
>
> Can you give this NFS patch (from Trond) a try please?
>
> (I don't think it is a very good idea for NFS to be using
> WRITEPAGE_ACTIVATE here. If NFS needs to have good write
> clustering off the end of the LRU, we need to go about it
> some other way.)
>
>
--
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-05 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2004-06-14 22:04 Ron Maeder
2004-06-15 3:19 ` Nick Piggin
2004-06-16 3:08 ` Nick Piggin
2004-06-16 6:37 ` Ron Maeder
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=Pine.LNX.4.60.0406051219130.749@stimpy \
--to=rlm@orionmulti.com \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=riel@surriel.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