[dpdk-dev] [PATCH v2 1/3] mem: fix hugepage mapping error messages

2016-10-05 Thread Thomas Monjalon
2016-10-04 20:07, Sergio Gonzalez Monroy: > On 04/10/2016 18:17, Jean Tourrilhes wrote: > > Running secondary is tricky due to the need to map the memory region > > at the right place in VM, which is whatever primary has chosen. If the > > base address for primary happens to by already mapped in th

[dpdk-dev] [PATCH v2 1/3] mem: fix hugepage mapping error messages

2016-10-05 Thread Jean Tourrilhes
On Wed, Oct 05, 2016 at 11:51:48AM +0200, Thomas Monjalon wrote: > > Applied, thanks > A rebase was necessary because of this patch: http://dpdk.org/commit/c00ae961 > Please check everything is OK. Tested today's master. Working as expected. Thanks ! Jean

[dpdk-dev] [PATCH v2 1/3] mem: fix hugepage mapping error messages

2016-10-04 Thread Sergio Gonzalez Monroy
On 04/10/2016 18:17, Jean Tourrilhes wrote: > Running secondary is tricky due to the need to map the memory region > at the right place in VM, which is whatever primary has chosen. If the > base address for primary happens to by already mapped in the > secondary, we will hit precisely these error m

[dpdk-dev] [PATCH v2 1/3] mem: fix hugepage mapping error messages

2016-10-04 Thread Jean Tourrilhes
Running secondary is tricky due to the need to map the memory region at the right place in VM, which is whatever primary has chosen. If the base address for primary happens to by already mapped in the secondary, we will hit precisely these error messages (depending if we fail on the config region o