On 06-Nov-19 7:37 AM, David Marchand wrote:
On Wed, Nov 6, 2019 at 7:16 AM Wangyu (Eric) wrote:
In 64K pagesize system, DPDK will read the size NIC need in
uio/uio1/maps/map1/size, when the size small than pagesize(e.g.,82599 is 16K),
dev->mem_resource[i].len will be 16K, but the mmap func
On 06-Nov-19 7:37 AM, David Marchand wrote:
On Wed, Nov 6, 2019 at 7:16 AM Wangyu (Eric) wrote:
In 64K pagesize system, DPDK will read the size NIC need in
uio/uio1/maps/map1/size, when the size small than pagesize(e.g.,82599 is 16K),
dev->mem_resource[i].len will be 16K, but the mmap func
On Wed, Nov 6, 2019 at 7:16 AM Wangyu (Eric) wrote:
>
>
> In 64K pagesize system, DPDK will read the size NIC need in
> uio/uio1/maps/map1/size, when the size small than pagesize(e.g.,82599 is
> 16K), dev->mem_resource[i].len will be 16K, but the mmap function applies for
> at least 1 page siz
On Tue, Nov 5, 2019 at 8:27 AM Wangyu (Turing Solution Development
Dep) wrote:
>
>
> NIC address conflicts on 64K pagesize when using multiple NICs,
> as system will mmap 64K pagesize for NIC,
> but dev->mem_resource[i].len is 16K.
Please, can you describe the problem you want to fix?
Is this a p
NIC address conflicts on 64K pagesize when using multiple NICs,
as system will mmap 64K pagesize for NIC,
but dev->mem_resource[i].len is 16K.
Signed-off-by: Beard-627
Signed-off-by: Eric wang
Acked-by: Wei Hu
Acked-by: Min Hu
---
drivers/bus/pci/linux/pci.c | 5 +
1 file changed, 5 ins
5 matches
Mail list logo
