From: zhong jiang <zhongjiang@huawei.com>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>
Cc: dan.j.williams@intel.com, hannes@cmpxchg.org, mhocko@suse.com,
linux-mm@kvack.org
Subject: Re: [PATCH] mm: respect pre-allocated storage mapping for memmap
Date: Tue, 17 Jan 2017 16:14:03 +0800 [thread overview]
Message-ID: <587DD24B.2000709@huawei.com> (raw)
In-Reply-To: <efc34702-7921-a91c-3002-691f083001d5@linux.vnet.ibm.com>
On 2017/1/16 22:43, Anshuman Khandual wrote:
> On 01/16/2017 07:08 PM, zhongjiang wrote:
>> From: zhong jiang <zhongjiang@huawei.com>
>>
>> At present, we skip the reservation storage by the driver for
>> the zone_dvice. but the free pages set aside for the memmap is
>> ignored. And since the free pages is only used as the memmap,
>> so we can also skip the corresponding pages.
> But these free pages used for memmap mapping should also be accounted
> inside the zone, no ?
That's confusing. because first_pfn for zone_device after reserve and free page for
memmap mapping. That is used as a actuallly pfn for zone_device.
Thanks
zhongjiang
> --
> 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>
>
>
--
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:[~2017-01-17 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 13:38 [PATCH] mm: respect pre-allocated storage mapping for memmap zhongjiang
2017-01-16 14:43 ` Anshuman Khandual
2017-01-17 8:14 ` zhong jiang [this message]
2017-01-17 10:25 ` Michal Hocko
2017-01-17 13:58 ` zhong jiang
2017-01-17 17:15 ` Dan Williams
2017-01-18 10:09 ` zhong jiang
2017-01-18 13:27 ` zhong jiang
2017-01-18 15:39 ` Dan Williams
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=587DD24B.2000709@huawei.com \
--to=zhongjiang@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=hannes@cmpxchg.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
/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.