linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jiang Liu <liuj97@gmail.com>
To: Simon Jeons <simon.jeons@gmail.com>
Cc: Jiang Liu <jiang.liu@huawei.com>,
	"linux-mm@kvack.org >> Linux Memory Management List"
	<linux-mm@kvack.org>
Subject: Re: mm: introduce new field "managed_pages" to struct zone
Date: Sun, 03 Mar 2013 23:43:48 +0800	[thread overview]
Message-ID: <51336FB4.9000202@gmail.com> (raw)
In-Reply-To: <512EF580.6000608@gmail.com>

Hi Simon,
	Bootmem allocator is used to managed DMA and Normal memory only, and it does not manage highmem pages because kernel
can't directly access highmem pages.
	Regards!
	Gerry

On 02/28/2013 02:13 PM, Simon Jeons wrote:
> Hi Jiang,
> 
> https://patchwork.kernel.org/patch/1781291/
> 
> You said that the bootmem allocator doesn't touch *highmem pages*, so highmem zones' managed_pages is set to the accurate value "spanned_pages - absent_pages" in function free_area_init_core() and won't be updated anymore. Why it doesn't touch *highmem pages*? Could you point out where you figure out this?
> 

--
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>

  parent reply	other threads:[~2013-03-03 15:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28  6:13 mm: introduce new field "managed_pages" to struct zone Simon Jeons
2013-03-03  5:01 ` Ric Mason
2013-03-03 17:13   ` Jiang Liu
2013-03-03 15:43 ` Jiang Liu [this message]
2013-03-03 23:57   ` Simon Jeons
2013-03-04 16:37     ` Jiang Liu
2013-03-05 12:19       ` Simon Jeons
2013-03-05 15:08         ` Jiang Liu
2013-03-06  0:21           ` Simon Jeons
2013-03-08  2:14             ` Simon Jeons
2013-03-08  3:11             ` Jiang Liu
2013-03-05 12:21       ` Simon Jeons
2013-03-05 15:03         ` Jiang Liu

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=51336FB4.9000202@gmail.com \
    --to=liuj97@gmail.com \
    --cc=jiang.liu@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=simon.jeons@gmail.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 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).