All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiaoyun wang <cloud.wangxiaoyun@huawei.com>
To: <dev@dpdk.org>
Cc: <ferruh.yigit@intel.com>, <bluca@debian.org>,
	<luoxianjun@huawei.com>, <luoxingyu@huawei.com>,
	<zhouguoyang@huawei.com>, <shahar.belkar@huawei.com>,
	 <yin.yinshi@huawei.com>, <david.yangxiaoliang@huawei.com>,
	<zhaohui8@huawei.com>, <zhengjingzhou@huawei.com>,
	Xiaoyun wang <cloud.wangxiaoyun@huawei.com>
Subject: [dpdk-dev] [PATCH v5 0/4] Support ipv6 flow rules
Date: Sat, 9 May 2020 12:04:12 +0800	[thread overview]
Message-ID: <cover.1588991713.git.cloud.wangxiaoyun@huawei.com> (raw)

This patch adds jumbo frame offload flag, increases
judgment whether Tx/Rx queues is non-null when free
resources, and if card mode does not support nic, 
driver will be initialized failed, supports ipv6
flow director for BGP or ICMP packets.

--
v4->v5:
  - increase Tx/Rx queues non-null judgment
  - add jumbo frame offload flag
  - increase judgment for support NIC or not
  - support ipv6 flow rules
  
v3->v4:
  - fix PF firmware hotactive problem
  - optimize log style
  - adds txq xstats members
  
v2->v3:
  - fix FW hotactive problem
  - optimize log style
  
v1->v2:
  - Fix LRO problems
  - Fix hotupdate firmware problem
  - Optimize doorbell area initialization 
  - Remove 40GE Mezz card id
  - Add Fdir filter type
  - Optimize log files
  - Support pause flow control

v1:
  - Allocate IO memory with socketid

Xiaoyun wang (4):
  net/hinic: increase Tx/Rx queues non-null judgment
  net/hinic: add jumbo frame offload flag
  net/hinic: increase judgment for support NIC or not
  net/hinic/base: support ipv6 flow rules

 drivers/net/hinic/base/hinic_pmd_cfg.c   |   3 +-
 drivers/net/hinic/base/hinic_pmd_cmdq.h  |   2 +-
 drivers/net/hinic/base/hinic_pmd_hwif.c  |   2 +-
 drivers/net/hinic/base/hinic_pmd_nicio.c |   1 -
 drivers/net/hinic/hinic_pmd_ethdev.c     |  32 +++--
 drivers/net/hinic/hinic_pmd_ethdev.h     |  57 ++++++++-
 drivers/net/hinic/hinic_pmd_flow.c       | 209 ++++++++++++++++++++++++++++---
 drivers/net/hinic/hinic_pmd_rx.c         |   3 +-
 drivers/net/hinic/hinic_pmd_tx.c         |   5 +-
 9 files changed, 281 insertions(+), 33 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2020-05-09  3:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09  4:04 Xiaoyun wang [this message]
2020-05-09  4:04 ` [dpdk-dev] [PATCH v5 1/4] net/hinic: increase Tx/Rx queues non-null judgment Xiaoyun wang
2020-05-11 19:09   ` Ferruh Yigit
2020-05-09  4:04 ` [dpdk-dev] [PATCH v5 2/4] net/hinic: add jumbo frame offload flag Xiaoyun wang
2020-05-09  4:04 ` [dpdk-dev] [PATCH v5 3/4] net/hinic: increase judgment for support NIC or not Xiaoyun wang
2020-05-09  4:04 ` [dpdk-dev] [PATCH v5 4/4] net/hinic/base: support ipv6 flow rules Xiaoyun wang
2020-05-11 20:12   ` Ferruh Yigit
2020-05-11 19:04 ` [dpdk-dev] [PATCH v5 0/4] Support " Ferruh Yigit
2020-05-11 20:20   ` 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=cover.1588991713.git.cloud.wangxiaoyun@huawei.com \
    --to=cloud.wangxiaoyun@huawei.com \
    --cc=bluca@debian.org \
    --cc=david.yangxiaoliang@huawei.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=luoxianjun@huawei.com \
    --cc=luoxingyu@huawei.com \
    --cc=shahar.belkar@huawei.com \
    --cc=yin.yinshi@huawei.com \
    --cc=zhaohui8@huawei.com \
    --cc=zhengjingzhou@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.