[dpdk-stable] [dpdk-dev] [PATCH v3] eal/mem: preallocate VA space in no-huge mode

[Zhou, JunX W]

Tested-by: Zhou, JunX W <junx.w.zhou at intel.com>
-----Original Message-----
From: Jiang, YuX 
Sent: Thursday, March 26, 2020 8:24 PM
To: David Marchand <david.marchand at redhat.com>; Burakov, Anatoly <anatoly.burakov at intel.com>
Cc: dev <dev at dpdk.org>; dpdk stable <stable at dpdk.org>; Zhou, JunX W <junx.w.zhou at intel.com>
Subject: RE: [dpdk-dev] [dpdk-stable] [PATCH v3] eal/mem: preallocate VA space in no-huge mode

+  Zhou, JunX W <junx.w.zhou at intel.com>

-----Original Message-----
From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of David Marchand
Sent: Wednesday, March 25, 2020 10:40 PM
To: Burakov, Anatoly <anatoly.burakov at intel.com>
Cc: dev <dev at dpdk.org>; dpdk stable <stable at dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v3] eal/mem: preallocate VA space in no-huge mode

On Fri, Feb 7, 2020 at 12:11 PM Anatoly Burakov <anatoly.burakov at intel.com> wrote:
>
> When --no-huge mode is used, the memory is currently allocated with 
> mmap(NULL, ...). This is fine in most cases, but can fail in cases 
> where DPDK is run on a machine with an IOMMU that is of more limited 
> address width than that of a VA, because we're not specifying the 
> address hint for mmap() call.
>
> Fix it by preallocating VA space before mapping it.
>
> Cc: stable at dpdk.org
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov at intel.com>

Reproduced issue reported by Thomas on v2.
Works fine with v3.

Tested-by: David Marchand <david.marchand at redhat.com>


Does this issue affect FreeBSD too?

--
David Marchand