[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1392091093.2501.7.camel@buesod1.americas.hpqcorp.net>
Date: Mon, 10 Feb 2014 19:58:13 -0800
From: Davidlohr Bueso <davidlohr@...com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Luiz Capitulino <lcapitulino@...hat.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, mtosatti@...hat.com, mgorman@...e.de,
aarcange@...hat.com, andi@...stfloor.org, riel@...hat.com
Subject: Re: [PATCH 0/4] hugetlb: add hugepagesnid= command-line option
On Mon, 2014-02-10 at 15:13 -0800, Andrew Morton wrote:
> On Mon, 10 Feb 2014 12:27:44 -0500 Luiz Capitulino <lcapitulino@...hat.com> wrote:
>
> > HugeTLB command-line option hugepages= allows the user to specify how many
> > huge pages should be allocated at boot. On NUMA systems, this argument
> > automatically distributes huge pages allocation among nodes, which can
> > be undesirable.
>
> Grumble. "can be undesirable" is the entire reason for the entire
> patchset. We need far, far more detail than can be conveyed in three
> words, please!
One (not so real-world) scenario that comes right to mind which can
benefit for such a feature is the ability to study socket/node scaling
for hugepage aware applications. Yes, we do have numactl to bind
programs to resources, but I don't mind having a way of finer graining
hugetlb allocations, specially if it doesn't hurt anything.
Thanks,
Davidlohr
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists