From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4424398F.2040300@yahoo.com.au> Date: Sat, 25 Mar 2006 05:25:19 +1100 From: Nick Piggin MIME-Version: 1.0 Subject: Re: [PATCH][5/8] proc: export mlocked pages info through "/proc/meminfo: Wired" References: <441FEFC7.5030109@yahoo.com.au> <442098B6.5000607@yahoo.com.au> <442420A2.80807@yahoo.com.au> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Rik van Riel Cc: Stone Wang , akpm@osdl.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: 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: email@kvack.org