From: Coywolf Qi Hunt <coywolf@gmail.com>
To: "akpm@osdl.org" <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
rmk+lkml@arm.linux.org.uk, rmk@arm.linux.org.uk
Subject: Re: [patch 006/198] arm: add comment about max_low_pfn/max_pfn
Date: Wed, 13 Apr 2005 11:10:35 +0800 [thread overview]
Message-ID: <2cd57c900504122010430af248@mail.gmail.com> (raw)
In-Reply-To: <200504121030.j3CAUie5005135@shell0.pdx.osdl.net>
I told rmk about this long time ago.
On 4/12/05, akpm@osdl.org <akpm@osdl.org> wrote:
>
> From: Russell King <rmk+lkml@arm.linux.org.uk>
>
> Oddly, max_low_pfn/max_pfn end up being the number of pages in the system,
> rather than the maximum PFN on ARM. This doesn't seem to cause any problems,
> so just add a note about it.
>
> Signed-off-by: Russell King <rmk@arm.linux.org.uk>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
>
> 25-akpm/arch/arm/mm/init.c | 3 +++
> 1 files changed, 3 insertions(+)
>
> diff -puN arch/arm/mm/init.c~arm-add-comment-about-max_low_pfn-max_pfn arch/arm/mm/init.c
> --- 25/arch/arm/mm/init.c~arm-add-comment-about-max_low_pfn-max_pfn 2005-04-12 03:21:04.967381744 -0700
> +++ 25-akpm/arch/arm/mm/init.c 2005-04-12 03:21:04.971381136 -0700
> @@ -223,6 +223,9 @@ find_memend_and_nodes(struct meminfo *mi
> * This doesn't seem to be used by the Linux memory
> * manager any more. If we can get rid of it, we
> * also get rid of some of the stuff above as well.
> + *
> + * Note: max_low_pfn and max_pfn reflect the number
> + * of _pages_ in the system, not the maximum PFN.
> */
> max_low_pfn = memend_pfn - O_PFN_DOWN(PHYS_OFFSET);
> max_pfn = memend_pfn - O_PFN_DOWN(PHYS_OFFSET);
> _
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
next prev parent reply other threads:[~2005-04-13 3:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 10:30 [patch 006/198] arm: add comment about max_low_pfn/max_pfn akpm
2005-04-13 3:10 ` Coywolf Qi Hunt [this message]
2005-04-13 4:18 ` Coywolf Qi Hunt
2005-04-13 7:44 ` Russell King
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=2cd57c900504122010430af248@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@osdl.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