From: Rusty Russell <rusty@rustcorp.com.au>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: num_physpages vs. totalram_pages
Date: Sun, 7 Jun 2009 09:38:02 +0930 [thread overview]
Message-ID: <200906070938.03131.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4A2938B302000078000049D7@vpn.id2.novell.com>
On Fri, 5 Jun 2009 10:54:35 pm Jan Beulich wrote:
> Rusty,
>
> in a mail from beginning of last year you indicated that the confusion
> between these two variables should be cleaned up. Since I wasn't able to
> spot any follow-up regarding this matter, I'm wondering what the plan here
> is. I'm asking because we have got customers reporting inconsistencies
> mainly caused by the use of num_physpages where totalram_pages would really
> be more appropriate (other than in your mail, where you mainly point at the
> networking code, this is with the determination of the number of files the
> system will use without admin involvement), due to large sparse areas in
> the physical address map.
>
> Unfortunately, the meaning of num_physpages seems to also vary between
> architectures (some treat it as being the same as totalram_pages) as well
> as subsystems (memory hotplug increments/decrements num_physpages along
> with totalram_pages).
Unfortunately, I have not even thought about it between then and now. I look
forward to your proposal!
Rusty.
prev parent reply other threads:[~2009-06-07 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 13:24 num_physpages vs. totalram_pages Jan Beulich
2009-06-07 0:08 ` Rusty Russell [this message]
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=200906070938.03131.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=JBeulich@novell.com \
--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