linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: zhenguo yao <yaozhenguo1@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mike.kravetz@oracle.com, corbet@lwn.net,
	linux-kernel@vger.kernel.org,  linux-doc@vger.kernel.org,
	linux-mm@kvack.org, yaozhenguo@jd.com,
	 Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] hugetlbfs: add hugepages_node kernel parameter
Date: Mon, 23 Aug 2021 10:04:59 +0800	[thread overview]
Message-ID: <CA+WzARkRYP=n1T+G3ciUYmM+nK3H-FpRMG5Nq8kpujTwpYmnMA@mail.gmail.com> (raw)
In-Reply-To: <20210822151952.23ca9547316dc34c9f3bd482@linux-foundation.org>

OK,  It's better to use a concise way to add this function.  I will
use a better way in the next version.

Andrew Morton <akpm@linux-foundation.org> 于2021年8月23日周一 上午6:19写道:
>
> On Fri, 20 Aug 2021 11:05:36 +0800 yaozhenguo <yaozhenguo1@gmail.com> wrote:
>
> > We can specify the number of hugepages to allocate at boot. But the
> > hugepages is balanced in all nodes at present. In some scenarios,
> > we only need hugepags in one node. For example: DPDK needs hugepages
> > which is in the same node as NIC. if DPDK needs four hugepags of 1G
> > size in node1 and system has 16 numa nodes. We must reserve 64 hugepags
> > in kernel cmdline. But, only four hugepages is used. The others should
> > be free after boot.If the system memory is low(for example: 64G), it will
> > be an impossible task. So, add hugepages_node kernel parameter to specify
> > node number of hugepages to allocate at boot.
> > For example add following parameter:
> >
> > hugepagesz=1G hugepages_node=1 hugepages=4
> >
> > It will allocate 4 hugepags in node1 at boot.
>
> If were going to do this, shouldn't we permit more than one node?
>
>         hugepages_nodes=1,2,5


      parent reply	other threads:[~2021-08-23  2:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20  3:05 yaozhenguo
2021-08-22 22:19 ` Andrew Morton
2021-08-22 22:27   ` Matthew Wilcox
2021-08-23  1:57     ` zhenguo yao
2021-08-23 16:52     ` Mike Kravetz
2021-08-23  2:04   ` zhenguo yao [this message]

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='CA+WzARkRYP=n1T+G3ciUYmM+nK3H-FpRMG5Nq8kpujTwpYmnMA@mail.gmail.com' \
    --to=yaozhenguo1@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=willy@infradead.org \
    --cc=yaozhenguo@jd.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