From: Matthew Wilcox <willy@infradead.org>
To: yhb@ruijie.com.cn
Cc: linux-mm@kvack.org
Subject: Re: memblock:What is the difference between memory and physmem?
Date: Sun, 12 Aug 2018 19:30:15 -0700 [thread overview]
Message-ID: <20180813023015.GB32733@bombadil.infradead.org> (raw)
In-Reply-To: <80B78A8B8FEE6145A87579E8435D78C3240515EF@FZEX4.ruijie.com.cn>
On Mon, Aug 13, 2018 at 02:23:26AM +0000, yhb@ruijie.com.cn wrote:
> struct memblock {
> bool bottom_up; /* is bottom up direction? */
> phys_addr_t current_limit;
> struct memblock_type memory;
> struct memblock_type reserved;
> #ifdef CONFIG_HAVE_MEMBLOCK_PHYS_MAP
> struct memblock_type physmem;
> #endif
> };
> What is the difference between memory and physmem?
commit 70210ed950b538ee7eb811dccc402db9df1c9be4
Author: Philipp Hachtmann <phacht@linux.vnet.ibm.com>
Date: Wed Jan 29 18:16:01 2014 +0100
mm/memblock: add physical memory list
Add the physmem list to the memblock structure. This list only exists
if HAVE_MEMBLOCK_PHYS_MAP is selected and contains the unmodified
list of physically available memory. It differs from the memblock
memory list as it always contains all memory ranges even if the
memory has been restricted, e.g. by use of the mem= kernel parameter.
Signed-off-by: Philipp Hachtmann <phacht@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
next prev parent reply other threads:[~2018-08-13 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 2:23 memblock:What is the difference between memory and physmem? yhb
2018-08-13 2:30 ` Matthew Wilcox [this message]
2018-08-13 14:36 ` Mike Rapoport
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=20180813023015.GB32733@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=linux-mm@kvack.org \
--cc=yhb@ruijie.com.cn \
/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).