All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC][ATTEND] a few topics I'd like to discuss
Date: Tue, 19 Feb 2013 11:30:12 +0000	[thread overview]
Message-ID: <20130219113012.GP4365@suse.de> (raw)
In-Reply-To: <5122E8C0.4020404@gmail.com>

On Mon, Feb 18, 2013 at 09:51:44PM -0500, KOSAKI Motohiro wrote:
> >> * Hugepage migration ? Currently, hugepage is not migratable and can?t
> >> use pages in ZONE_MOVABLE.  It is not happy from point of CMA/hotplug
> >> view.
> >>
> > 
> > migrate_huge_page() ?
> > 
> > It's also possible to allocate hugetlbfs pages in ZONE_MOVABLE but must
> > be enabled via /proc/sys/vm/hugepages_treat_as_movable.
> 
> Oops. I missed that. Sorry for noise.
> 
> But but... I wonder why this knob is disabled by default. I don't think anybody
> get a benefit form current default.
> 

It's disabled by default simply because at the time the pages were not
movable at all. They now should be movable with some additional work and
potentially the default could change after that or be removed entirely.

-- 
Mel Gorman
SUSE Labs

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

  reply	other threads:[~2013-02-19 11:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-17  6:44 [LSF/MM TOPIC][ATTEND] a few topics I'd like to discuss KOSAKI Motohiro
2013-02-17  7:28 ` Will Huck
2013-02-18 14:50 ` [Lsf-pc] " Mel Gorman
2013-02-19  2:51   ` KOSAKI Motohiro
2013-02-19 11:30     ` Mel Gorman [this message]
2013-02-19 21:44       ` KOSAKI Motohiro
2013-02-20 11:03   ` Simon Jeons
2013-02-23  3:02     ` KOSAKI Motohiro

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=20130219113012.GP4365@suse.de \
    --to=mgorman@suse.de \
    --cc=kosaki.motohiro@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.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.