From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Rik van Riel <riel@redhat.com>
Cc: Stone Wang <pwstone@gmail.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH][5/8] proc: export mlocked pages info through "/proc/meminfo: Wired"
Date: Sat, 25 Mar 2006 05:25:19 +1100 [thread overview]
Message-ID: <4424398F.2040300@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.63.0603241319130.30426@cuia.boston.redhat.com>
Rik van Riel wrote:
> On Sat, 25 Mar 2006, Nick Piggin wrote:
>
>>Rik van Riel wrote:
>>
>>>On Wed, 22 Mar 2006, Nick Piggin wrote:
>>>
>>>
>>>>Why would you want to ever do something like that though? I don't think
>>>>you should use this name "just in case", unless you have some really good
>>>>potential usage in mind.
>>>
>>>ramfs
>>
>>Why would ramfs want its pages in this wired list? (I'm not so
>>familiar with it but I can't think of a reason).
>
>
> Because ramfs pages cannot be paged out, which makes them locked
> into memory the same way mlocked pages are.
>
I don't understand why they need to be on any list though,
that isn't an internal ramfs specific structure (ie. not
the just-in-case wired list).
--
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: Rik van Riel <riel@redhat.com>
Cc: Stone Wang <pwstone@gmail.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH][5/8] proc: export mlocked pages info through "/proc/meminfo: Wired"
Date: Sat, 25 Mar 2006 05:25:19 +1100 [thread overview]
Message-ID: <4424398F.2040300@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.63.0603241319130.30426@cuia.boston.redhat.com>
Rik van Riel wrote:
> On Sat, 25 Mar 2006, Nick Piggin wrote:
>
>>Rik van Riel wrote:
>>
>>>On Wed, 22 Mar 2006, Nick Piggin wrote:
>>>
>>>
>>>>Why would you want to ever do something like that though? I don't think
>>>>you should use this name "just in case", unless you have some really good
>>>>potential usage in mind.
>>>
>>>ramfs
>>
>>Why would ramfs want its pages in this wired list? (I'm not so
>>familiar with it but I can't think of a reason).
>
>
> Because ramfs pages cannot be paged out, which makes them locked
> into memory the same way mlocked pages are.
>
I don't understand why they need to be on any list though,
that isn't an internal ramfs specific structure (ie. not
the just-in-case wired list).
--
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:[~2006-03-24 19:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 13:37 [PATCH][5/8] proc: export mlocked pages info through "/proc/meminfo: Wired" Stone Wang
2006-03-20 13:37 ` Stone Wang
2006-03-21 12:21 ` Nick Piggin
2006-03-21 12:21 ` Nick Piggin
2006-03-21 15:33 ` Stone Wang
2006-03-21 15:33 ` Stone Wang
2006-03-21 19:43 ` Arjan van de Ven
2006-03-21 19:43 ` Arjan van de Ven
2006-03-22 0:22 ` Nick Piggin
2006-03-22 0:22 ` Nick Piggin
2006-03-22 5:37 ` Stone Wang
2006-03-22 5:37 ` Stone Wang
2006-03-22 7:23 ` Nick Piggin
2006-03-22 7:23 ` Nick Piggin
2006-03-22 9:04 ` Arjan van de Ven
2006-03-22 9:04 ` Arjan van de Ven
2006-03-24 16:34 ` Rik van Riel
2006-03-24 16:34 ` Rik van Riel
2006-03-24 16:38 ` Nick Piggin
2006-03-24 16:38 ` Nick Piggin
2006-03-24 18:19 ` Rik van Riel
2006-03-24 18:19 ` Rik van Riel
2006-03-24 18:25 ` Nick Piggin [this message]
2006-03-24 18:25 ` Nick Piggin
2006-03-21 21:43 ` Dave Hansen
2006-03-21 21:43 ` Dave Hansen
2006-03-22 6:02 ` Stone Wang
2006-03-22 6:02 ` Stone Wang
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=4424398F.2040300@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pwstone@gmail.com \
--cc=riel@redhat.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 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.