linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@surriel.com>
To: Ron Maeder <rlm@orionmulti.com>
Cc: linux-mm@kvack.org
Subject: Re: mmap() > phys mem problem
Date: Fri, 28 May 2004 22:08:55 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.55L.0405282208210.32578@imladris.surriel.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0405251523250.18898-100000@pygar.sc.orionmulti.com>

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
-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
--
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>

  reply	other threads:[~2004-05-29  2:08 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 [this message]
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
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.55L.0405282208210.32578@imladris.surriel.com \
    --to=riel@surriel.com \
    --cc=linux-mm@kvack.org \
    --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