From: "Stone Wang" <pwstone@gmail.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: PATCH][1/8] 2.6.15 mlock: make_pages_wired/unwired
Date: Wed, 22 Mar 2006 03:59:33 -0500 [thread overview]
Message-ID: <bc56f2f0603220059x6b2a30b8h@mail.gmail.com> (raw)
In-Reply-To: <44209A26.3040102@yahoo.com.au>
2006/3/21, Nick Piggin <nickpiggin@yahoo.com.au>:
> Stone Wang wrote:
> > We dont account HugeTLB pages for:
> >
> > 1. HugeTLB pages themselves are not reclaimable.
> >
> > 2. If we count HugeTLB pages in "Wired",then we would have no mind
> > how many of the "Wired" are HugeTLB pages, and how many are
> > normal-size pages.
> > Thus, hard to get a clear map of physical memory use,for example:
> > how many pages are reclaimable?
> > If we must count HugeTLB pages,more fields should be added to
> > "/proc/meminfo",
> > for exmaple: "Wired HugeTLB:", "Wired Normal:".
> >
>
> Then why do you wire them at all? Your unwire function does not appear
> to be able to unwire them.
We didnt wire them.
Check get_user_pages():
/* We dont account wired HugeTLB pages */
if (is_vm_hugetlb_page(vma)) {
i = follow_hugetlb_page(mm, vma, pages, vmas,
&start, &len, i);
continue;
}
Shaoping Wang
>
> --
> 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 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 13:36 Stone Wang
2006-03-20 13:42 ` Arjan van de Ven
2006-03-21 12:21 ` Nick Piggin
2006-03-21 16:03 ` Stone Wang
2006-03-22 0:28 ` Nick Piggin
2006-03-22 8:59 ` Stone Wang [this message]
2006-03-22 10:13 ` Nick Piggin
2006-03-22 11:59 ` 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=bc56f2f0603220059x6b2a30b8h@mail.gmail.com \
--to=pwstone@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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