From: "Wangyu (Turing Solution Development Dep)" <seven.wangyu@huawei.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
Linuxarm <linuxarm@huawei.com>, "humin (Q)" <humin29@huawei.com>,
"Liyuan (Larry)" <Larry.T@huawei.com>,
dengxiaofeng <dengxiaofeng@huawei.com>
Subject: [dpdk-dev] [PATCH] bus/pci: resolve multiple NICs address conflicts
Date: Mon, 4 Nov 2019 06:31:39 +0000 [thread overview]
Message-ID: <78A93308629D474AA53B84C5879E84D24B0FF99F@DGGEMM533-MBX.china.huawei.com> (raw)
In-Reply-To: <1572680245-89705-1-git-send-email-dengxiaofeng@huawei.com>
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 <dengxiaofeng@huawei.com>
Acked-by: Eric wang <seven.wangyu@huawei.com>
Acked-by: Wei Hu <xavier.huwei@huawei.com>
Acked-by: Min Hu <humin29@huawei.com>
---
drivers/bus/pci/linux/pci.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/bus/pci/linux/pci.c b/drivers/bus/pci/linux/pci.c index 43debaa..afaa68d 100644
--- a/drivers/bus/pci/linux/pci.c
+++ b/drivers/bus/pci/linux/pci.c
@@ -201,6 +201,11 @@
if (flags & IORESOURCE_MEM) {
dev->mem_resource[i].phys_addr = phys_addr;
dev->mem_resource[i].len = end_addr - phys_addr + 1;
+ if (dev->mem_resource[i].len <
+ (unsigned int)getpagesize())
+
+ dev->mem_resource[i].len =
+ (unsigned int)getpagesize();
/* not mapped for now */
dev->mem_resource[i].addr = NULL;
}
--
1.8.3.1
parent reply other threads:[~2019-11-04 6:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1572680245-89705-1-git-send-email-dengxiaofeng@huawei.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78A93308629D474AA53B84C5879E84D24B0FF99F@DGGEMM533-MBX.china.huawei.com \
--to=seven.wangyu@huawei.com \
--cc=Larry.T@huawei.com \
--cc=dengxiaofeng@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.com \
--cc=linuxarm@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).