From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Wangyu (Eric)" <seven.wangyu@huawei.com>,
dengxiaofeng <dengxiaofeng@huawei.com>,
David Marchand <david.marchand@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
Linuxarm <linuxarm@huawei.com>, "humin (Q)" <humin29@huawei.com>,
"Liyuan (Larry)" <Larry.T@huawei.com>
Subject: Re: [dpdk-dev] 答复: [PATCH v2] bus/pci: resolve multiple NICs address conflicts
Date: Wed, 6 Nov 2019 10:29:52 +0000 [thread overview]
Message-ID: <a1a7cfdd-605e-6da0-88f7-f2e5e28838e6@intel.com> (raw)
In-Reply-To: <78A93308629D474AA53B84C5879E84D24B103B0C@DGGEMM533-MBX.china.huawei.com>
On 06-Nov-19 6:15 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 size, which is 64K.
> Then second NIC mmap, start address is first NIC address + 16K, which already used by first NIC.
> So if change the size to first NIC address + 64K, problem solved.
>
It seems like something that should be fixed at the mapping stage,
rather than modifying length of the resources.
--
Thanks,
Anatoly
prev parent reply other threads:[~2019-11-06 10:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 7:26 [dpdk-dev] " Wangyu (Turing Solution Development Dep)
2019-11-05 14:33 ` David Marchand
[not found] ` <D3165BB52137B64493C4E18DC69F10D62C8E7CDC@DGGEMM501-MBX.china.huawei.com>
2019-11-06 6:15 ` [dpdk-dev] 答复: " Wangyu (Eric)
2019-11-06 7:37 ` [dpdk-dev] " David Marchand
2019-11-06 10:35 ` Burakov, Anatoly
[not found] ` <D3165BB52137B64493C4E18DC69F10D62C8E903A@DGGEMM501-MBX.china.huawei.com>
2019-11-07 3:17 ` [dpdk-dev] 答复: " Wangyu (Eric)
2019-11-06 11:14 ` [dpdk-dev] " Burakov, Anatoly
[not found] ` <D3165BB52137B64493C4E18DC69F10D62C8E9085@DGGEMM501-MBX.china.huawei.com>
2019-11-07 5:44 ` [dpdk-dev] 答复: " Wangyu (Eric)
2019-11-07 12:24 ` Burakov, Anatoly
[not found] ` <D3165BB52137B64493C4E18DC69F10D62C8F159A@dggemm521-mbx.china.huawei.com>
2019-11-11 9:37 ` [dpdk-dev] 答复: " Wangyu (Eric)
2019-11-11 13:07 ` Burakov, Anatoly
2019-11-12 6:37 ` Gavin Hu (Arm Technology China)
2019-11-06 10:29 ` Burakov, Anatoly [this message]
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=a1a7cfdd-605e-6da0-88f7-f2e5e28838e6@intel.com \
--to=anatoly.burakov@intel.com \
--cc=Larry.T@huawei.com \
--cc=david.marchand@redhat.com \
--cc=dengxiaofeng@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.com \
--cc=linuxarm@huawei.com \
--cc=seven.wangyu@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).