[dpdk-dev] [PATCH v3] eal: fix memory mapping for 32-bit targets

2021-05-08 Thread Lance Richardson
For 32-bit targets, size_t is normally a 32-bit type and does not have sufficient range to represent 64-bit offsets that can are needed when mapping PCI addresses. Use uint64_t instead. Found when attempting to run 32-bit Linux dpdk-testpmd using VFIO driver: EAL: pci_map_resource(): cannot m

Re: [dpdk-dev] [PATCH v3] eal: fix memory mapping for 32-bit targets

2021-05-10 Thread Thomas Monjalon
+Cc Anatoly 08/05/2021 16:27, Lance Richardson: > For 32-bit targets, size_t is normally a 32-bit type and > does not have sufficient range to represent 64-bit offsets > that can are needed when mapping PCI addresses. Use uint64_t > instead. > > Found when attempting to run 32-bit Linux dpdk-test

Re: [dpdk-dev] [PATCH v3] eal: fix memory mapping for 32-bit targets

2021-05-10 Thread Burakov, Anatoly
On 10-May-21 1:42 PM, Thomas Monjalon wrote: +Cc Anatoly 08/05/2021 16:27, Lance Richardson: For 32-bit targets, size_t is normally a 32-bit type and does not have sufficient range to represent 64-bit offsets that can are needed when mapping PCI addresses. Use uint64_t instead. Found when atte

Re: [dpdk-dev] [PATCH v3] eal: fix memory mapping for 32-bit targets

2021-05-10 Thread Thomas Monjalon
10/05/2021 17:31, Burakov, Anatoly: > On 10-May-21 1:42 PM, Thomas Monjalon wrote: > > +Cc Anatoly > > > > 08/05/2021 16:27, Lance Richardson: > >> For 32-bit targets, size_t is normally a 32-bit type and > >> does not have sufficient range to represent 64-bit offsets > >> that can are needed when

Re: [dpdk-dev] [PATCH v3] eal: fix memory mapping for 32-bit targets

2021-05-10 Thread Lance Richardson
On Mon, May 10, 2021 at 11:55 AM Thomas Monjalon wrote: > 10/05/2021 17:31, Burakov, Anatoly: > > On 10-May-21 1:42 PM, Thomas Monjalon wrote: > > > +Cc Anatoly > > > > > > 08/05/2021 16:27, Lance Richardson: > > >> For 32-bit targets, size_t is normally a 32-bit type and > > >> does not have suf

Re: [dpdk-dev] [PATCH v3] eal: fix memory mapping for 32-bit targets

2021-05-11 Thread Thomas Monjalon
08/05/2021 16:27, Lance Richardson: > For 32-bit targets, size_t is normally a 32-bit type and > does not have sufficient range to represent 64-bit offsets > that can are needed when mapping PCI addresses. Use uint64_t > instead. > > Found when attempting to run 32-bit Linux dpdk-testpmd > using V

Re: [dpdk-dev] [PATCH v3] eal: fix memory mapping for 32-bit targets

2021-05-11 Thread Lance Richardson
On Tue, May 11, 2021 at 4:18 AM Thomas Monjalon wrote: > > 08/05/2021 16:27, Lance Richardson: > > For 32-bit targets, size_t is normally a 32-bit type and > > does not have sufficient range to represent 64-bit offsets > > that can are needed when mapping PCI addresses. Use uint64_t > > instead. >

Re: [dpdk-dev] [PATCH v3] eal: fix memory mapping for 32-bit targets

2021-05-11 Thread Thomas Monjalon
10/05/2021 17:31, Burakov, Anatoly: > On 10-May-21 1:42 PM, Thomas Monjalon wrote: > > +Cc Anatoly > > > > 08/05/2021 16:27, Lance Richardson: > >> For 32-bit targets, size_t is normally a 32-bit type and > >> does not have sufficient range to represent 64-bit offsets > >> that can are needed when