kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: chandanrmail@gmail.com (chandan r)
To: kernelnewbies@lists.kernelnewbies.org
Subject: MAX_PHYSADDR_BITS v/s MAX_PHYSMEM_BITS
Date: Tue, 20 Dec 2011 19:04:59 +0530	[thread overview]
Message-ID: <20111220133459.GA1831@archlinux> (raw)

Hi all,

   Consider the following code snippet (for x86_64 arch) from
arch/x86/include/asm/sparsemem.h:

# define SECTION_SIZE_BITS	27 /* matt - 128 is convenient right now */
# define MAX_PHYSADDR_BITS	44
# define MAX_PHYSMEM_BITS	46

Also, consider the following comments (obtained from the same file),

MAX_PHYSADDR_BITS		2^n: max size of physical address space
MAX_PHYSMEM_BITS		2^n: how much memory we can have in
				     that space

According to my understanding MAX_PHYSMEM_BITS has to have a value
less than or equal to MAX_PHYSADDR_BITS. But this is not the case
for x86_64. Can someone explain what these macros really mean?

Thanks,
chandan r

                 reply	other threads:[~2011-12-20 13:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20111220133459.GA1831@archlinux \
    --to=chandanrmail@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).