From: David Marchand <david.marchand@redhat.com>
To: "Wangyu (Turing Solution Development Dep)" <seven.wangyu@huawei.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>,
dengxiaofeng <dengxiaofeng@huawei.com>
Subject: Re: [dpdk-dev] [PATCH v2] bus/pci: resolve multiple NICs address conflicts
Date: Tue, 5 Nov 2019 15:33:12 +0100 [thread overview]
Message-ID: <CAJFAV8yxryiK9bmgHv6qoMBFCp+QLeXo0Opu2drqwppGAcVgBQ@mail.gmail.com> (raw)
In-Reply-To: <78A93308629D474AA53B84C5879E84D24B102602@DGGEMM533-MBX.china.huawei.com>
On Tue, Nov 5, 2019 at 8:27 AM Wangyu (Turing Solution Development
Dep) <seven.wangyu@huawei.com> 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 problem specific to a pci device you are using?
Thanks.
>
> Signed-off-by: Beard-627 <dengxiaofeng@huawei.com>
> Signed-off-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
--
David Marchand
next prev parent reply other threads:[~2019-11-05 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 7:26 Wangyu (Turing Solution Development Dep)
2019-11-05 14:33 ` David Marchand [this message]
[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 ` [dpdk-dev] " Burakov, Anatoly
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=CAJFAV8yxryiK9bmgHv6qoMBFCp+QLeXo0Opu2drqwppGAcVgBQ@mail.gmail.com \
--to=david.marchand@redhat.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 \
--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).