From: "Iram Shahzad" <iram.shahzad@jp.fujitsu.com>
To: linux-mm@kvack.org
Cc: mel@csn.ul.ie
Subject: compaction: why depends on HUGETLB_PAGE
Date: Thu, 29 Jul 2010 10:53:12 +0900 [thread overview]
Message-ID: <D25878F935704D9281E62E0393CAD951@rainbow> (raw)
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?
Is it wrong to use it on ARM by disabling CONFIG_HUGETLB_PAGE?
Iram
--
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 reply other threads:[~2010-07-29 1:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 1:53 Iram Shahzad [this message]
2010-07-29 12:57 ` Mel Gorman
2010-07-30 2:56 ` Iram Shahzad
2010-07-30 9:57 ` Mel Gorman
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=D25878F935704D9281E62E0393CAD951@rainbow \
--to=iram.shahzad@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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