From: Thomas Monjalon <thomas@monjalon.net>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, "Pattan, Reshma" <reshma.pattan@intel.com>,
"Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>
Subject: Re: [PATCH v3 3/3] mem: improve autodetection of hugepage counts on 32-bit
Date: Fri, 27 Apr 2018 23:47:11 +0200 [thread overview]
Message-ID: <4370618.qW8ombCSU7@xps> (raw)
In-Reply-To: <3AEA2BF9852C6F48A459DA490692831F2A2C9B5B@irsmsx110.ger.corp.intel.com>
> > For non-legacy mode, we are preallocating space for hugepages, so we know
> > in advance which pages we will be able to allocate, and which we won't.
> > However, the init procedure was using hugepage counts gathered from sysfs
> > and paid no attention to hugepage sizes that were actually available for
> > reservation, and failed on attempts to reserve unavailable pages.
> >
> > Fix this by limiting total page counts by number of pages actually
> > preallocated.
> >
> > Also, VA preallocate procedure only looks at mountpoints that are available,
> > and expects pages to exist if a mountpoint exists. That might not necessarily
> > be the case, so also check if there are hugepages available for a particular
> > page size on a particular NUMA node.
> >
> > Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
>
> Tested-by: Jananee Parthasarathy <jananeex.m.parthasarathy@intel.com>
Series applied, thanks
next prev parent reply other threads:[~2018-04-27 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 14:41 [PATCH 1/3] mem: fix 32-bit memory upper limit for non-legacy mode Anatoly Burakov
2018-04-20 14:41 ` [PATCH 2/3] mem: improve memory preallocation on 32-bit Anatoly Burakov
2018-04-20 14:41 ` [PATCH 3/3] mem: improve autodetection of hugepage counts " Anatoly Burakov
2018-04-20 15:12 ` Burakov, Anatoly
2018-04-20 15:25 ` [PATCH v2 1/3] mem: fix 32-bit memory upper limit for non-legacy mode Anatoly Burakov
2018-04-24 10:19 ` [PATCH v3 " Anatoly Burakov
2018-04-25 13:26 ` Pattan, Reshma
2018-04-24 10:19 ` [PATCH v3 2/3] mem: improve memory preallocation on 32-bit Anatoly Burakov
2018-04-25 13:27 ` Pattan, Reshma
2018-04-24 10:19 ` [PATCH v3 3/3] mem: improve autodetection of hugepage counts " Anatoly Burakov
2018-04-25 13:28 ` Pattan, Reshma
2018-04-27 21:47 ` Thomas Monjalon [this message]
2018-04-20 15:25 ` [PATCH v2 2/3] mem: improve memory preallocation " Anatoly Burakov
2018-04-20 15:25 ` [PATCH v2 3/3] mem: improve autodetection of hugepage counts " Anatoly Burakov
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=4370618.qW8ombCSU7@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=jananeex.m.parthasarathy@intel.com \
--cc=reshma.pattan@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.