DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ziyang Xuan <xuanziyang2@huawei.com>, dev@dpdk.org
Cc: cloud.wangxiaoyun@huawei.com, shahar.belkar@huawei.com,
	luoxianjun@huawei.com, tanya.brokhman@huawei.com
Subject: Re: [dpdk-dev] [PATCH v6 00/15] A new net PMD - hinic
Date: Thu, 27 Jun 2019 15:26:21 +0100	[thread overview]
Message-ID: <b7d987c0-3c6e-1274-e88d-1d1567ca7f38@intel.com> (raw)
In-Reply-To: <cover.1561620219.git.xuanziyang2@huawei.com>

On 6/27/2019 9:10 AM, 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
> 
> v6:
>  - Adjust hinic pmd maintainers
>  - Use "CONFIG_RTE_ARCH_X86_64" to determine X86_64 for SSE instruction
>  - Fix "check-git-log.sh" checking errors
>  - Move "hinic_pmd_ethdev.h" to patch 11/15, and
>    "hinic_pmd_rx.h"/"hinic_pmd_tx.h" to patch 12/15
> 
> 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/base: 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 Rx/Tx package burst
>   net/hinic: add RSS stats promiscuous ops

For series,
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Series applied to dpdk-next-net/master, thanks.


This is first PMD from Huawei, welcome to dpdk, thanks for your efforts.

  parent reply	other threads:[~2019-06-27 14:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27  8:10 Ziyang Xuan
2019-06-27  8:11 ` [dpdk-dev] [PATCH v6 01/15] net/hinic/base: add HW registers definition Ziyang Xuan
2019-06-27  8:12 ` [dpdk-dev] [PATCH v6 02/15] net/hinic/base: add HW interfaces of bar operation Ziyang Xuan
2019-06-27  8:13 ` [dpdk-dev] [PATCH v6 03/15] net/hinic/base: add API command channel code Ziyang Xuan
2019-06-27  8:14 ` [dpdk-dev] [PATCH v6 04/15] net/hinic/base: add support for cmdq mechanism Ziyang Xuan
2019-06-27  8:14 ` [dpdk-dev] [PATCH v6 05/15] net/hinic/base: add eq mechanism function code Ziyang Xuan
2019-06-27  8:15 ` [dpdk-dev] [PATCH v6 06/15] net/hinic/base: add mgmt module " Ziyang Xuan
2019-06-27  8:15 ` [dpdk-dev] [PATCH v6 07/15] net/hinic/base: add code about hardware operation Ziyang Xuan
2019-06-27  8:16 ` [dpdk-dev] [PATCH v6 08/15] net/hinic/base: add NIC business configurations Ziyang Xuan
2019-06-27  8:17 ` [dpdk-dev] [PATCH v6 09/15] net/hinic/base: add context and work queue support Ziyang Xuan
2019-06-27  8:17 ` [dpdk-dev] [PATCH v6 10/15] net/hinic/base: add various headers Ziyang Xuan
2019-06-27  8:18 ` [dpdk-dev] [PATCH v6 11/15] net/hinic: add hinic PMD build and doc files Ziyang Xuan
2019-10-29 15:50   ` Stephen Hemminger
2019-10-29 16:27     ` Andrew Rybchenko
2019-11-04 10:55       ` Bruce Richardson
2019-06-27  8:18 ` [dpdk-dev] [PATCH v6 12/15] net/hinic: add device initailization Ziyang Xuan
2019-06-27  8:19 ` [dpdk-dev] [PATCH v6 13/15] net/hinic: add start stop close queue ops Ziyang Xuan
2019-06-27  8:19 ` [dpdk-dev] [PATCH v6 14/15] net/hinic: add Rx/Tx package burst Ziyang Xuan
2019-07-11 13:59   ` Ferruh Yigit
2019-06-27  8:20 ` [dpdk-dev] [PATCH v6 15/15] net/hinic: add RSS stats promiscuous ops Ziyang Xuan
2019-06-27 14:26 ` Ferruh Yigit [this message]
2019-10-26 14:43   ` [dpdk-dev] [PATCH v6 00/15] A new net PMD - hinic David Marchand
2019-10-29  6:43     ` Wangxiaoyun (Cloud, Network Chip Application Development Dept)
2019-10-29  7:23       ` David Marchand

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=b7d987c0-3c6e-1274-e88d-1d1567ca7f38@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=tanya.brokhman@huawei.com \
    --cc=xuanziyang2@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).