From: Andi Kleen <andi@firstfloor.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Davidlohr Bueso <davidlohr@hp.com>,
David Rientjes <rientjes@google.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
mtosatti@redhat.com, Mel Gorman <mgorman@suse.de>,
Andrea Arcangeli <aarcange@redhat.com>,
Andi Kleen <andi@firstfloor.org>, Rik van Riel <riel@redhat.com>,
isimatu.yasuaki@jp.fujitsu.com, yinghai@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 4/4] hugetlb: add hugepages_node= command-line option
Date: Sat, 22 Feb 2014 05:03:50 +0100 [thread overview]
Message-ID: <20140222040350.GI22728@two.firstfloor.org> (raw)
In-Reply-To: <20140221155423.6c6689e27fa10ed394f01843@linux-foundation.org>
> But I think it would be better if it made hugepages= and hugepagesz=
> obsolete, so we can emit a printk if people use those, telling them
> to migrate because the old options are going away.
Not sure why everyone wants to break existing systems. These options
have existed for many years, you cannot not just remove them.
Also the old options are totally fine and work adequately for the
vast majority of users who do not need to control node assignment
fine grained.
-Andi
--
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:[~2014-02-22 4:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 1:02 [PATCH v2 0/4] hugetlb: add hugepages_node= command-line option Luiz Capitulino
2014-02-14 1:02 ` [PATCH 1/4] memblock: memblock_virt_alloc_internal(): add __GFP_THISNODE flag support Luiz Capitulino
2014-02-14 1:02 ` [PATCH 2/4] memblock: add memblock_virt_alloc_nid_nopanic() Luiz Capitulino
2014-02-14 1:02 ` [PATCH 3/4] hugetlb: add parse_pagesize_str() Luiz Capitulino
2014-02-14 1:02 ` [PATCH 4/4] hugetlb: add hugepages_node= command-line option Luiz Capitulino
2014-02-14 23:14 ` David Rientjes
2014-02-15 3:58 ` Luiz Capitulino
2014-02-15 10:06 ` David Rientjes
2014-02-17 13:56 ` Luiz Capitulino
2014-02-17 23:23 ` David Rientjes
2014-02-18 12:30 ` Marcelo Tosatti
2014-02-18 22:16 ` David Rientjes
2014-02-20 2:22 ` Marcelo Tosatti
2014-02-20 3:46 ` David Rientjes
2014-02-20 4:42 ` Luiz Capitulino
2014-02-20 4:51 ` David Rientjes
2014-02-20 15:06 ` Luiz Capitulino
2014-02-20 21:34 ` Marcelo Tosatti
2014-02-20 23:15 ` David Rientjes
2014-02-21 2:28 ` Marcelo Tosatti
2014-02-21 10:07 ` David Rientjes
2014-02-21 19:10 ` Marcelo Tosatti
2014-02-21 22:04 ` David Rientjes
2014-02-21 22:36 ` Andi Kleen
2014-02-21 22:44 ` David Rientjes
2014-02-21 22:55 ` Andi Kleen
2014-02-21 3:35 ` Luiz Capitulino
2014-02-20 21:38 ` Marcelo Tosatti
2014-02-20 23:17 ` David Rientjes
2014-02-18 5:47 ` Davidlohr Bueso
2014-02-21 23:54 ` Andrew Morton
2014-02-22 4:03 ` Andi Kleen [this message]
2014-02-22 4:31 ` Davidlohr Bueso
2014-02-22 4:40 ` Andrew Morton
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=20140222040350.GI22728@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davidlohr@hp.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mtosatti@redhat.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=yinghai@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).