From: moreau francis <francis_moreau2000@yahoo.fr>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re : Re : Re : sparsemem usage
Date: Thu, 3 Aug 2006 12:46:28 +0000 (GMT) [thread overview]
Message-ID: <20060803124628.21540.qmail@web25805.mail.ukl.yahoo.com> (raw)
In-Reply-To: <44D1C616.1060305@shadowen.org>
Andy Whitcroft wrote:
> That would be incorrect usage. pfn_valid() simply doesn't tell you if
> you have memory backing a pfn, it mearly means you can interrogate the
> page* for it. A good example of code which counts pages in a region is
> in count_highmem_pages() which has a form as below:
>
> for (pfn = start; pfn < end; pfn++) {
> if (!pfn_valid(pfn))
> continue;
> page = pfn_to_page(pfn);
> if (PageReserved(page))
> continue;
> num_physpages++;
> }
>
num_physpages would still not give the right total number of pages in the
system. It will report a value smaller than the size of all memories which can
be suprising, depending on how it is used. In my mind I thought that it should
store the number of all pages in the system (reserved + free + ...).
Futhermore for flatmem model, my example that count the number of physical
pages is valid: reserved pages are really pages that are in used by the kernel.
But it's not valid anymore for sparsemem model. For consistency and code
sharing, I would make the same meaning of pfn_valid() and PageReserved() for
both models.
Francis
next prev parent reply other threads:[~2006-08-03 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 9:07 moreau francis
2006-08-03 9:19 ` KAMEZAWA Hiroyuki
2006-08-03 9:47 ` Andy Whitcroft
2006-08-03 12:46 ` moreau francis [this message]
2006-08-03 13:13 ` Re : " Andy Whitcroft
2006-08-09 14:19 ` Re : " moreau francis
2006-08-10 4:46 ` KAMEZAWA Hiroyuki
2006-08-10 12:40 ` moreau francis
2006-08-10 12:49 ` KAMEZAWA Hiroyuki
2006-08-11 8:26 Re : " Andy Whitcroft
2006-08-11 12:46 ` Re : " moreau francis
2006-08-11 12:52 ` Andy Whitcroft
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=20060803124628.21540.qmail@web25805.mail.ukl.yahoo.com \
--to=francis_moreau2000@yahoo.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®