From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Stone Wang <pwstone@gmail.com>
Cc: 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: Wed, 22 Mar 2006 11:22:14 +1100 [thread overview]
Message-ID: <442098B6.5000607@yahoo.com.au> (raw)
In-Reply-To: <bc56f2f0603210733vc3ce132p@mail.gmail.com>
Stone Wang wrote:
> The list potentially could have more wider use.
>
> For example, kernel-space locked/pinned pages could be placed on the list too
> (while mlocked pages are locked/pinned by system calls from user-space).
>
kernel-space pages are always pinned. And no, you can't put them on the list
because you never know if their ->lru field is going to be used for something
else.
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.
---
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-22 0:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 13:37 Stone Wang
2006-03-21 12:21 ` Nick Piggin
2006-03-21 15:33 ` Stone Wang
2006-03-21 19:43 ` Arjan van de Ven
2006-03-22 0:22 ` Nick Piggin [this message]
2006-03-22 5:37 ` Stone Wang
2006-03-22 7:23 ` Nick Piggin
2006-03-22 9:04 ` Arjan van de Ven
2006-03-24 16:34 ` Rik van Riel
2006-03-24 16:38 ` Nick Piggin
2006-03-24 18:19 ` Rik van Riel
2006-03-24 18:25 ` Nick Piggin
2006-03-21 21:43 ` Dave Hansen
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=442098B6.5000607@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 \
/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