From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ziyang Xuan <xuanziyang2@huawei.com>, dev@dpdk.org
Cc: cloud.wangxiaoyun@huawei.com, zhouguoyang@huawei.com,
shahar.belkar@huawei.com, luoxianjun@huawei.com
Subject: Re: [dpdk-dev] [PATCH v5 00/15] A new net PMD - hinic
Date: Wed, 26 Jun 2019 12:56:07 +0100 [thread overview]
Message-ID: <1d0e86fa-e987-fc28-5b39-4813324d901c@intel.com> (raw)
In-Reply-To: <cover.1560958308.git.xuanziyang2@huawei.com>
On 6/19/2019 4:45 PM, Ziyang Xuan wrote:
> This patch set adds support of a new net PMD
> for Huawei Intelligent nic. This patch provides supoort
> for basic RX/TX and the contorl path needed for it.
> Later on new features will be added like VLAN, VFs, etc.
>
> Basic features:
> 1. Basic device operations: probe, initialization, start/stop,
> configure, info get.
> 2. RX/TX queue operations: setup/release, start/stop.
> 3. RX/TX.
>
> Stats:
> 1. statistics and extended statistics.
>
> ---
> v2:
> - Fix arm64 compilation issue.
> - Fix some checkpatch checks issues
> - Fix patches thread issue.
> - Fit to the newest rte_ prefix patch
>
> v3:
> - Remove Rami from hinic pmd maintainers
> - Remove hinic_logs.* files and move log codes to other files
> - Remove the C++ guards within hinic pmd codes
> - Remove variable related errors shields from compilation files
> - Use lib link statu related functions but selfdefined
> - Fix x86_64-native-linuxapp-clang compilation errors
> - Fix i686-native-linuxapp-gcc compilation errors
>
> v4:
> - Update doc hinic.ini and hinic.rst
> - Remove x86-32, i686, BSD, Power8, ARMv7 compilations
> - Fit to newest IPV4 and IPV6 uppercase
>
> v5:
> - Update doc hinic.rst and release_19_08.rst
> - Delete unused codes
> - Optimize arch of codes and delete unnecessary files
> - Remove rte_panic
> - Subdivided patches
>
> Ziyang Xuan (15):
> net/hinic/base: add HW registers definition
> net/hinic/base: add HW interfaces of bar operation
> net/hinic/base: add api command channel code
> net/hinic/base: add support for cmdq mechanism
> net/hinic/base: add eq mechanism function code
> net/hinic/base: add mgmt module function code
> net/hinic/base: add code about hardware operation
> net/hinic/base: add nic business configurations
> net/hinic/base: add context and work queue support
> net/hinic: add various headers
> net/hinic: add hinic PMD build and doc files
> net/hinic: add device initailization
> net/hinic: add start stop close queue ops
> net/hinic: add tx/rx package burst
> net/hinic: add rss stats promisc ops
Hi Ziyang,
I put a few minor comments on patches, other than those looks good.
Also can you please run "./devtools/check-git-log.sh", I think it will give some
warnings on commit log syntax, can you please check them?
Thanks,
ferruh
next prev parent reply other threads:[~2019-06-26 11:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 15:45 Ziyang Xuan
2019-06-19 15:46 ` [dpdk-dev] [PATCH v5 01/15] net/hinic/base: add HW registers definition Ziyang Xuan
2019-06-19 15:50 ` [dpdk-dev] [PATCH v5 02/15] net/hinic/base: add HW interfaces of bar operation Ziyang Xuan
2019-06-19 15:47 ` Ziyang Xuan
2019-06-19 15:54 ` [dpdk-dev] [PATCH v5 03/15] net/hinic/base: add api command channel code Ziyang Xuan
2019-06-19 15:55 ` [dpdk-dev] [PATCH v5 04/15] net/hinic/base: add support for cmdq mechanism Ziyang Xuan
2019-06-19 15:56 ` [dpdk-dev] [PATCH v5 05/15] net/hinic/base: add eq mechanism function code Ziyang Xuan
2019-06-19 15:57 ` [dpdk-dev] [PATCH v5 06/15] net/hinic/base: add mgmt module " Ziyang Xuan
2019-06-19 16:02 ` [dpdk-dev] [PATCH v5 07/15] net/hinic/base: add code about hardware operation Ziyang Xuan
2019-06-19 15:58 ` Ziyang Xuan
2019-06-19 16:04 ` [dpdk-dev] [PATCH v5 08/15] net/hinic/base: add nic business configurations Ziyang Xuan
2019-06-19 16:05 ` [dpdk-dev] [PATCH v5 09/15] net/hinic/base: add context and work queue support Ziyang Xuan
2019-06-19 16:08 ` [dpdk-dev] [PATCH v5 10/15] net/hinic: add various headers Ziyang Xuan
2019-06-26 11:54 ` Ferruh Yigit
2019-06-19 16:09 ` [dpdk-dev] [PATCH v5 11/15] net/hinic: add hinic PMD build and doc files Ziyang Xuan
2019-06-19 16:13 ` Ziyang Xuan
2019-06-26 11:55 ` Ferruh Yigit
2019-06-19 16:16 ` [dpdk-dev] [PATCH v5 12/15] net/hinic: add device initailization Ziyang Xuan
2019-06-19 16:14 ` Ziyang Xuan
2019-06-19 16:30 ` Ziyang Xuan
2019-06-19 16:18 ` [dpdk-dev] [PATCH v5 13/15] net/hinic: add start stop close queue ops Ziyang Xuan
2019-06-19 16:32 ` Ziyang Xuan
2019-06-19 16:20 ` [dpdk-dev] [PATCH v5 14/15] net/hinic: add tx/rx package burst Ziyang Xuan
2019-06-19 16:25 ` Ziyang Xuan
2019-06-26 11:54 ` Ferruh Yigit
2019-06-26 15:58 ` [dpdk-dev] 答复: " Xuanziyang (William, Chip Application Design Logic and Hardware Development Dept IT_Products & Solutions)
2019-06-26 16:05 ` Ferruh Yigit
2019-06-19 16:23 ` [dpdk-dev] [PATCH v5 15/15] net/hinic: add rss stats promisc ops Ziyang Xuan
2019-06-26 11:56 ` Ferruh Yigit [this message]
2019-06-26 14:42 [dpdk-dev] [PATCH v5 00/15] A new net PMD - hinic Xuanziyang (William, Chip Application Design Logic and Hardware Development Dept IT_Products & Solutions)
2019-06-26 16:48 ` Ferruh Yigit
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=1d0e86fa-e987-fc28-5b39-4813324d901c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=dev@dpdk.org \
--cc=luoxianjun@huawei.com \
--cc=shahar.belkar@huawei.com \
--cc=xuanziyang2@huawei.com \
--cc=zhouguoyang@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).