From: Guoyang Zhou <zhouguoyang@huawei.com>
To: <dev@dpdk.org>
Cc: <ferruh.yigit@intel.com>, <bluca@debian.org>,
<cloud.wangxiaoyun@huawei.com>, <luoxianjun@huawei.com>,
<yin.yinshi@huawei.com>, <luojiachen@huawei.com>,
<zhouguoyang@huawei.com>, <chenlizhong@huawei.com>,
<zhaohui8@huawei.com>, <chenchanghu@huawei.com>
Subject: [dpdk-dev] [PATCH v2 0/2] remove some limitations and operations
Date: Tue, 24 Nov 2020 14:45:32 +0800 [thread overview]
Message-ID: <cover.1606199729.git.zhouguoyang@huawei.com> (raw)
The maximum number of queues on the chip can be any value greater
than 0, it does not have to be the power of two, if it does not be
fixed, dpdk initialization may be failed with OVS mode firmware
and remove the operation of optical modules in the link function, because
when device binds from dpdk to kernel, it will be linked failed.
--
v1->v2:
- add some necessary comments for patches
- correct fixed patch id
v1:
- remove the limitation for max queue num
- remove the operation of optical modules in the link function
Guoyang Zhou (2):
net/hinic/base: remove the limitation for max queue num
net/hinic: remove the operation of optical modules
drivers/net/hinic/base/hinic_pmd_niccfg.c | 38 -------------------------------
drivers/net/hinic/base/hinic_pmd_niccfg.h | 2 --
drivers/net/hinic/base/hinic_pmd_nicio.c | 5 ----
drivers/net/hinic/hinic_pmd_ethdev.c | 14 ------------
4 files changed, 59 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-11-24 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 6:45 Guoyang Zhou [this message]
2020-11-24 6:45 ` [dpdk-dev] [PATCH v2 1/2] net/hinic/base: remove the limitation for max queue num Guoyang Zhou
2020-11-24 6:45 ` [dpdk-dev] [PATCH v2 2/2] net/hinic: remove the operation of optical modules Guoyang Zhou
2020-11-25 22:33 ` [dpdk-dev] [PATCH v2 0/2] remove some limitations and operations Thomas Monjalon
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=cover.1606199729.git.zhouguoyang@huawei.com \
--to=zhouguoyang@huawei.com \
--cc=bluca@debian.org \
--cc=chenchanghu@huawei.com \
--cc=chenlizhong@huawei.com \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=luojiachen@huawei.com \
--cc=luoxianjun@huawei.com \
--cc=yin.yinshi@huawei.com \
--cc=zhaohui8@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).