From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
To: wangyunjian <wangyunjian@huawei.com>,
"dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: Huangshaozhang <huangshaozhang@huawei.com>,
dingxiaoxiong <dingxiaoxiong@huawei.com>
Subject: RE: [dpdk-dev] [dpdk-users] A question about Mellanox ConnectX-5 and ConnectX-4 Lx nic can't send packets?
Date: Tue, 11 Jan 2022 07:36:34 +0000 [thread overview]
Message-ID: <BN8PR12MB289903D60FD1FDA6442DDE7FB9519@BN8PR12MB2899.namprd12.prod.outlook.com> (raw)
In-Reply-To: <6232d9136c60431a9ea72b83b9a4760a@huawei.com>
Hello,
Thanks for attaching all the details.
Can you please reproduce it with --log-level=pmd.common.mlx5:debug
and send the logs?
> For example, if the environment is configured with 10GB hugepages
> but each hugepage is physically discontinuous, this problem
> can be reproduced.
What the hugepage size?
In general, net/mlx5 does not rely on physical addresses.
(You probably mean that a range of hugepages is discontiguous,
because **each** hugepage is contiguous by definition.)
> This problem is introduced by this patch:
> https://git.dpdk.org/dpdk/commit/?id=fec28ca0e3a93143829f3b41a28a8da933f28499.
Did you find it with bisection?
next prev parent reply other threads:[~2022-01-11 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 6:08 wangyunjian
2022-01-11 7:36 ` Dmitry Kozlyuk [this message]
2022-01-11 8:21 ` wangyunjian
2022-01-11 11:42 ` Dmitry Kozlyuk
2022-01-11 12:29 ` wangyunjian
2022-01-12 4:21 ` wangyunjian
2022-01-11 8:45 ` wangyunjian
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=BN8PR12MB289903D60FD1FDA6442DDE7FB9519@BN8PR12MB2899.namprd12.prod.outlook.com \
--to=dkozlyuk@nvidia.com \
--cc=dev@dpdk.org \
--cc=dingxiaoxiong@huawei.com \
--cc=huangshaozhang@huawei.com \
--cc=matan@nvidia.com \
--cc=users@dpdk.org \
--cc=viacheslavo@nvidia.com \
--cc=wangyunjian@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).