All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Iram Shahzad <iram.shahzad@jp.fujitsu.com>
Cc: linux-mm@kvack.org
Subject: Re: compaction: why depends on HUGETLB_PAGE
Date: Thu, 29 Jul 2010 13:57:25 +0100	[thread overview]
Message-ID: <20100729125725.GA3571@csn.ul.ie> (raw)
In-Reply-To: <D25878F935704D9281E62E0393CAD951@rainbow>

On Thu, Jul 29, 2010 at 10:53:12AM +0900, Iram Shahzad wrote:
> Hi
>
> I have found that memory compaction (CONFIG_COMPACTION)
> is mainlined while looking at 2.6.35-rc5 source code.
> I have a question regarding its dependency on HUGETLB_PAGE.
>
> While trying to use CONFIG_COMPACTION on ARM architecture,
> I found that I cannot enable CONFIG_COMPACTION because
> it depends on CONFIG_HUGETLB_PAGE which is not available
> on ARM.
>
> I disabled the dependency and was able to build it.
> And it looks like working!
>
> My question is: why does it depend on CONFIG_HUGETLB_PAGE?

Because as the Kconfig says "Allows the compaction of memory for the
allocation of huge pages.". Depending on compaction to satisfy other
high-order allocation types is not likely to be a winning strategy.

> Is it wrong to use it on ARM by disabling CONFIG_HUGETLB_PAGE?
>

It depends on why you need compaction. If it's for some device that
requires high-order allocations (particularly if they are atomic), then
it's not likely to work very well in the long term.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
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:[~2010-07-29 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29  1:53 compaction: why depends on HUGETLB_PAGE Iram Shahzad
2010-07-29 12:57 ` Mel Gorman [this message]
2010-07-30  2:56   ` Iram Shahzad
2010-07-30  9:57     ` Mel Gorman
  -- strict thread matches above, loose matches on Subject: below --
2010-07-30 16:44 Round Robinjp
2010-07-30 16:49 ` 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=20100729125725.GA3571@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=iram.shahzad@jp.fujitsu.com \
    --cc=linux-mm@kvack.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.