Re: [PATCH v5 0/2] Balanced allocation of hugepages

Hi everyone,

I just want to clarify current status of these patches.
As I understand, moving to the new build system (for example,
meson+ninja as proposed[1] by Bruce) is a very long process.
But we have issues with imbalanced memory allocation now, and
IMHO it's better to fix them in a near future.

Latest version (v5) of balanced allocation patches adds linbuma
as general unconditional dependency which conflicts with the
current DPDK policies.

So, there are 2 option:

	1. Return back config option RTE_LIBRTE_EAL_NUMA_AWARE_HUGEPAGES
	   from the first version of the patch and disable it by default.

	2. Keep patch as it is now and make everyone install libnuma
	   for successful build.

I have no preferences about above options. I'm asking your opinions.

Bruce, Sergio, Thomas, what do you think?

[1] http://dpdk.org/ml/archives/dev/2017-June/067428.html

Best regards, Ilya Maximets.

On 06.06.2017 16:33, Ilya Maximets wrote:

Sorry for so frequent respinning of the series.

Version 5:
	* Fixed shared build. (Automated build test will fail
	  anyway because libnuma-devel not installed on build servers)

Version 4:
	* Fixed work on systems without NUMA by adding check for NUMA
	  support in kernel.

Version 3:
	* Implemented hybrid schema for allocation.
	* Fixed not needed mempolicy change while remapping. (orig = 0)
	* Added patch to enable VHOST_NUMA by default.

Version 2:
	* rebased (fuzz in Makefile)

Ilya Maximets (2):
  mem: balanced allocation of hugepages
  config: enable vhost numa awareness by default

 config/common_base                       |  2 +-
 lib/librte_eal/linuxapp/eal/Makefile     |  1 +
 lib/librte_eal/linuxapp/eal/eal_memory.c | 94 ++++++++++++++++++++++++++++++--
 mk/rte.app.mk                            |  3 +
 4 files changed, 95 insertions(+), 5 deletions(-)