From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Track mlock()ed pages
Date: Fri, 26 Jan 2007 23:00:05 +1100 [thread overview]
Message-ID: <45B9ED45.5090002@yahoo.com.au> (raw)
In-Reply-To: <20070126031300.59f75b06.akpm@osdl.org>
Andrew Morton wrote:
> On Thu, 25 Jan 2007 22:36:17 -0800 (PST)
> Christoph Lameter <clameter@sgi.com> wrote:
>
>>>I can't think of an easy way to do this without per-page state. ie.
>>>another page flag.
>>
>>Thats what I am trying to avoid.
>
>
> You could perhaps go for a walk across all the other vmas which presently
> map this page. If any of them have VM_LOCKED, don't increment the counter.
> Similar on removal: only decrement the counter when the final mlocked VMA
> is dropping the pte.
Can't do with un-racily because you can't get that information
atomically, AFAIKS. When / if we ever lock the page in fault handler,
this could become easier... but that seems nasty to do in fault path,
even if only for VM_LOCKED vmas.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Track mlock()ed pages
Date: Fri, 26 Jan 2007 23:00:05 +1100 [thread overview]
Message-ID: <45B9ED45.5090002@yahoo.com.au> (raw)
In-Reply-To: <20070126031300.59f75b06.akpm@osdl.org>
Andrew Morton wrote:
> On Thu, 25 Jan 2007 22:36:17 -0800 (PST)
> Christoph Lameter <clameter@sgi.com> wrote:
>
>>>I can't think of an easy way to do this without per-page state. ie.
>>>another page flag.
>>
>>Thats what I am trying to avoid.
>
>
> You could perhaps go for a walk across all the other vmas which presently
> map this page. If any of them have VM_LOCKED, don't increment the counter.
> Similar on removal: only decrement the counter when the final mlocked VMA
> is dropping the pte.
Can't do with un-racily because you can't get that information
atomically, AFAIKS. When / if we ever lock the page in fault handler,
this could become easier... but that seems nasty to do in fault path,
even if only for VM_LOCKED vmas.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-01-26 12:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 5:43 [RFC] Track mlock()ed pages Christoph Lameter
2007-01-26 5:43 ` Christoph Lameter
2007-01-26 6:30 ` Nick Piggin
2007-01-26 6:30 ` Nick Piggin
2007-01-26 6:36 ` Christoph Lameter
2007-01-26 6:36 ` Christoph Lameter
2007-01-26 11:13 ` Andrew Morton
2007-01-26 11:13 ` Andrew Morton
2007-01-26 12:00 ` Nick Piggin [this message]
2007-01-26 12:00 ` Nick Piggin
2007-01-26 15:44 ` Christoph Lameter
2007-01-26 15:44 ` Christoph Lameter
2007-01-26 18:10 ` Andrew Morton
2007-01-26 18:10 ` Andrew Morton
2007-01-26 18:21 ` KAMEZAWA Hiroyuki
2007-01-26 18:21 ` KAMEZAWA Hiroyuki
2007-01-26 18:23 ` Christoph Lameter
2007-01-26 18:23 ` Christoph Lameter
2007-01-26 18:42 ` Andrew Morton
2007-01-26 18:42 ` Andrew Morton
2007-01-27 22:19 ` Rik van Riel
2007-01-27 22:19 ` Rik van Riel
2007-01-27 22:30 ` Andrew Morton
2007-01-27 22:30 ` Andrew Morton
2007-01-27 22:36 ` Rik van Riel
2007-01-27 22:36 ` Rik van Riel
2007-01-26 11:46 ` Nick Piggin
2007-01-26 11:46 ` 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=45B9ED45.5090002@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.