Re: [dpdk-dev] [PATCH] build: fix memory init failures with 32-bit builds

2020-07-05 Thread Thomas Monjalon
02/07/2020 13:19, Ferruh Yigit: > On 7/2/2020 11:57 AM, Bruce Richardson wrote: > > When building with meson, the default size of virtual address space > > reserved for mapping pages was globally set at 512GB, which is too big for > > use in 32-bit processes. To match the behaviour with "make", we

Re: [dpdk-dev] [PATCH] build: fix memory init failures with 32-bit builds

2020-07-02 Thread Ferruh Yigit
On 7/2/2020 11:57 AM, Bruce Richardson wrote: > When building with meson, the default size of virtual address space > reserved for mapping pages was globally set at 512GB, which is too big for > use in 32-bit processes. To match the behaviour with "make", we configure > this to be 512GB for 64-bit

Re: [dpdk-dev] [PATCH] build: fix memory init failures with 32-bit builds

2020-07-02 Thread Bruce Richardson
On Thu, Jul 02, 2020 at 11:57:21AM +0100, Bruce Richardson wrote: > When building with meson, the default size of virtual address space > reserved for mapping pages was globally set at 512GB, which is too big for > use in 32-bit processes. To match the behaviour with "make", we configure > this to

[dpdk-dev] [PATCH] build: fix memory init failures with 32-bit builds

2020-07-02 Thread Bruce Richardson
When building with meson, the default size of virtual address space reserved for mapping pages was globally set at 512GB, which is too big for use in 32-bit processes. To match the behaviour with "make", we configure this to be 512GB for 64-bit and 2MB for 32-bit builds. Bugzilla ID: 498 Fixes: 66