From: Sedat Dilek <sedat.dilek@googlemail.com>
To: LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: mm/Kconfig: warning: (COMPACTION && EXPERIMENTAL && HUGETLB_PAGE && MMU) selects MIGRATION which has unmet direct dependencies (NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE)
Date: Thu, 9 Sep 2010 17:15:22 +0200 [thread overview]
Message-ID: <AANLkTinoR=ZeCqcqSuoY884y_7MNB50B7RiwY4B+Fycc@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=uzLJxDbd+uJAww-b5aP10gd8gbGVG19HS46ue@mail.gmail.com>
Argh, forgot...
[ mm/Kconfig ]
...
#
# support for page migration
#
config MIGRATION
bool "Page migration"
def_bool y
depends on NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE
help
Allows the migration of the physical location of pages of processes
while the virtual addresses are not changed. This is useful in
two situations. The first is on NUMA systems to put pages nearer
to the processors accessing. The second is when allocating huge
pages as migration can relocate pages to satisfy a huge page
allocation instead of reclaiming.
...
- Sedat -
On Thu, Sep 9, 2010 at 5:10 PM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> Hi,
>
> while build latest 2.6.36-rc3 I get this warning:
>
> [ build.log]
> ...
> warning: (COMPACTION && EXPERIMENTAL && HUGETLB_PAGE && MMU) selects
> MIGRATION which has unmet direct dependencies (NUMA ||
> ARCH_ENABLE_MEMORY_HOTREMOVE)
> ...
>
> Here the excerpt of...
>
> [ mm/Kconfig ]
> ...
> # support for memory compaction
> config COMPACTION
> bool "Allow for memory compaction"
> select MIGRATION
> depends on EXPERIMENTAL && HUGETLB_PAGE && MMU
> help
> Allows the compaction of memory for the allocation of huge pages.
> ...
>
> I have set the following kernel-config parameters:
>
> $ egrep 'COMPACTION|HUGETLB_PAGE|MMU|MIGRATION|NUMA|ARCH_ENABLE_MEMORY_HOTREMOVE'
> linux-2.6.36-rc3/debian/build/build_i386_none_686/.config
> CONFIG_MMU=y
> # CONFIG_IOMMU_HELPER is not set
> CONFIG_IOMMU_API=y
> CONFIG_COMPACTION=y
> CONFIG_MIGRATION=y
> CONFIG_MMU_NOTIFIER=y
> CONFIG_HUGETLB_PAGE=y
> # CONFIG_IOMMU_STRESS is not set
>
> Looks like I have no NUMA or ARCH_ENABLE_MEMORY_HOTREMOVE set.
>
> Ok, it is a *warning*...
>
> Kind Regards,
> - Sedat -
>
--
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 prev parent reply other threads:[~2010-09-09 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 15:10 Sedat Dilek
2010-09-09 15:15 ` Sedat Dilek [this message]
2010-09-09 15:23 ` Randy Dunlap
2010-09-09 16:05 ` Sedat Dilek
2010-09-09 16:16 ` Sedat Dilek
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='AANLkTinoR=ZeCqcqSuoY884y_7MNB50B7RiwY4B+Fycc@mail.gmail.com' \
--to=sedat.dilek@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sedat.dilek@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