From: Peter Zijlstra <peterz@infradead.org>
To: Bob Walters <bob.s.walters@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mlock'ed pages are paging out to shared mapped files?
Date: Fri, 26 Nov 2010 17:36:21 +0100 [thread overview]
Message-ID: <1290789381.2145.154.camel@laptop> (raw)
In-Reply-To: <03A305FE-2E9E-42B0-A06C-564E03295B2A@gmail.com>
On Fri, 2010-11-26 at 11:25 -0500, Bob Walters wrote:
>
> Please CC directly, I'm not subscribed.
>
> I'm writing to determine if observed mlock behavior is a bug or the
> intended implementation. The kernel seems to be paging out
> modifications made to locked pages of a shared (MAP_SHARED) memory
> mapped regular file, on Linux 2.6.35.6-48 (Fedora 14 distro, x86_64).
> Man pages implies that this might be a bug. I have a repeatable
> process involving the following test:
That's not paged-out, its a shared mapping (ie a mapped file), you dirty
the pages, we clean them by writing them out to disk.
That is the expected behaviour, if the man-page implies anything else
its bonkers.
prev parent reply other threads:[~2010-11-26 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 16:25 mlock'ed pages are paging out to shared mapped files? Bob Walters
2010-11-26 16:36 ` Peter Zijlstra [this message]
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=1290789381.2145.154.camel@laptop \
--to=peterz@infradead.org \
--cc=bob.s.walters@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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