From: Will Huck <will.huckk@gmail.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Tang Chen <tangchen@cn.fujitsu.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"jiang.liu@huawei.com" <jiang.liu@huawei.com>,
"wujianguo@huawei.com" <wujianguo@huawei.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"wency@cn.fujitsu.com" <wency@cn.fujitsu.com>,
"laijs@cn.fujitsu.com" <laijs@cn.fujitsu.com>,
"linfeng@cn.fujitsu.com" <linfeng@cn.fujitsu.com>,
"yinghai@kernel.org" <yinghai@kernel.org>,
"isimatu.yasuaki@jp.fujitsu.com" <isimatu.yasuaki@jp.fujitsu.com>,
"rob@landley.net" <rob@landley.net>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
"minchan.kim@gmail.com" <minchan.kim@gmail.com>,
"mgorman@suse.de" <mgorman@suse.de>,
"rientjes@google.com" <rientjes@google.com>,
"guz.fnst@cn.fujitsu.com" <guz.fnst@cn.fujitsu.com>,
"rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
"lliubbo@gmail.com" <lliubbo@gmail.com>,
"jaegeuk.hanse@gmail.com" <jaegeuk.hanse@gmail.com>,
"glommer@parallels.com" <glommer@parallels.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [Bug fix PATCH 1/2] acpi, movablemem_map: Exclude memblock.reserved ranges when parsing SRAT.
Date: Thu, 21 Feb 2013 08:05:05 +0800 [thread overview]
Message-ID: <512564B1.8020008@gmail.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F1E06B55D@ORSMSX108.amr.corp.intel.com>
Hi Tony,
On 02/21/2013 06:41 AM, Luck, Tony wrote:
>> What's the relationship between e820 map and SRAT?
> The e820 map (or EFI memory map on some recent systems) provides
> a list of memory ranges together with usage information (e.g. reserved
> for BIOS, or available) and attributes (WB cacheable, uncacheable).
>
> The SRAT table provides topology information for address ranges. It
> tells the OS which memory is close to each cpu, and which is more
> distant. If there are multiple degrees of "distant" then the SLIT table
> provides a matrix of relative latencies between nodes.
Thanks for your clarify. What's the relationship between memory ranges
and address ranges here?
What's the relationship between memory/address ranges and /proc/iomem?
>
> -Tony
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-02-21 0:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 11:00 [Bug fix PATCH 0/2] Make whatever node kernel resides in un-hotpluggable Tang Chen
2013-02-20 11:00 ` Tang Chen
2013-02-20 11:00 ` [Bug fix PATCH 1/2] acpi, movablemem_map: Exclude memblock.reserved ranges when parsing SRAT Tang Chen
2013-02-20 11:00 ` Tang Chen
2013-02-20 12:31 ` Tang Chen
2013-02-20 12:31 ` Tang Chen
2013-02-20 12:35 ` Will Huck
2013-02-20 12:35 ` Will Huck
2013-02-20 22:41 ` Luck, Tony
2013-02-21 0:05 ` Will Huck [this message]
2013-02-21 0:23 ` Luck, Tony
2013-02-25 7:07 ` Will Huck
2013-02-25 9:01 ` Will Huck
2013-02-25 1:35 ` Will Huck
2013-02-25 3:32 ` Tang Chen
2013-02-25 19:06 ` Luck, Tony
2013-02-20 11:00 ` [Bug fix PATCH 2/2] acpi, movablemem_map: Make whatever nodes the kernel resides in un-hotpluggable Tang Chen
2013-02-20 11:00 ` Tang Chen
2013-02-23 19:26 ` Rob Landley
2013-02-23 19:26 ` Rob Landley
2013-02-25 2:54 ` Tang Chen
2013-02-25 2:54 ` Tang Chen
2013-02-20 21:36 ` [Bug fix PATCH 0/2] Make whatever node " Andrew Morton
2013-02-20 21:36 ` Andrew Morton
2013-02-21 3:03 ` Tang Chen
2013-02-21 3:03 ` Tang Chen
2013-02-21 7:03 ` Tang Chen
2013-02-21 7:03 ` Tang Chen
2013-02-23 19:40 ` Rob Landley
2013-02-23 19:40 ` Rob Landley
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=512564B1.8020008@gmail.com \
--to=will.huckk@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=glommer@parallels.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jaegeuk.hanse@gmail.com \
--cc=jiang.liu@huawei.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linfeng@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--cc=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=rientjes@google.com \
--cc=rob@landley.net \
--cc=rusty@rustcorp.com.au \
--cc=tangchen@cn.fujitsu.com \
--cc=tony.luck@intel.com \
--cc=wency@cn.fujitsu.com \
--cc=wujianguo@huawei.com \
--cc=yinghai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.