From: Ed Tomlinson <edt@aei.ca>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linux-kernel@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: How movable is zone movable?
Date: Mon, 13 Apr 2009 08:10:58 -0400 [thread overview]
Message-ID: <200904130810.59230.edt@aei.ca> (raw)
In-Reply-To: <20090413100440.GB15333@csn.ul.ie>
On Monday 13 April 2009 06:04:40 you wrote:
> On Mon, Apr 13, 2009 at 10:59:25AM +0100, Mel Gorman wrote:
> > > # huge_pages with movablecore set to 3G
> >
> > How big did you make the movable zone and what is the hugepage size?
>
> Scratch that question, I missed you said it was 3G. Are pages being
> mlocked()?
Looks like there are mlocked pages. What stopped the patches to allow these pages
to be migrated?
TIA
Ed
(from /proc/zoneinfo)
Node 0, zone Movable
pages free 35321
min 858
low 1072
high 1287
scanned 0 (aa: 2 ia: 0 af: 0 if: 0)
spanned 786432
present 775680
nr_free_pages 35321
nr_inactive_anon 29383
nr_active_anon 82452
nr_inactive_file 376826
nr_active_file 219586
nr_unevictable 816
nr_mlock 816
nr_anon_pages 110648
nr_mapped 28364
nr_file_pages 598492
nr_dirty 131
nr_writeback 0
nr_slab_reclaimable 0
nr_slab_unreclaimable 0
nr_page_table_pages 0
nr_unstable 0
nr_bounce 0
nr_vmscan_write 95
nr_writeback_temp 0
protection: (0, 0, 0, 0)
pagesets
cpu: 0
count: 7
high: 186
batch: 31
vm stats threshold: 24
cpu: 1
count: 7
high: 186
batch: 31
vm stats threshold: 24
cpu: 2
count: 14
high: 186
batch: 31
vm stats threshold: 24
all_unreclaimable: 0
prev_priority: 12
start_pfn: 1441792
inactive_ratio: 4
next prev parent reply other threads:[~2009-04-13 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 15:29 Ed Tomlinson
2009-04-13 1:04 ` KAMEZAWA Hiroyuki
2009-04-13 9:59 ` Mel Gorman
2009-04-13 10:04 ` Mel Gorman
2009-04-13 12:10 ` Ed Tomlinson [this message]
2009-04-14 9:18 ` Mel Gorman
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=200904130810.59230.edt@aei.ca \
--to=edt@aei.ca \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=npiggin@suse.de \
/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
Powered by JetHome