DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lijun Ou <oulijun@huawei.com>
To: <ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>, <linuxarm@openeuler.org>
Subject: [dpdk-dev] [PATCH 00/11] critical bugfixes for hns3
Date: Wed, 3 Feb 2021 20:23:46 +0800	[thread overview]
Message-ID: <1612355037-48768-1-git-send-email-oulijun@huawei.com> (raw)

Based on some suggestions, we reorganize the fixes
and resend the only fixes.

Chengchang Tang (4):
  net/hns3: fix stats flip overflow
  net/hns3: replace all atomic type with C11 atomic builtins
  net/hns3: fix cmdq cleared during firmware process
  net/hns3: fix VF reset after MBX failed

Chengwen Feng (3):
  net/hns3: constraint TM peak rate
  net/hns3: remove MPLS type from supported flow items
  net/hns3: fix FD rule residue in hardware when malloc fail

Huisong Li (3):
  net/hns3: fix query order of link status and link info
  net/hns3: fix link status change from firmware
  net/hns3: add check for max pkt length of Rx

Lijun Ou (1):
  net/hns3: fix RSS indirection table size

 drivers/net/hns3/hns3_cmd.c       |  36 ++++++++++--
 drivers/net/hns3/hns3_cmd.h       |  18 +++++-
 drivers/net/hns3/hns3_dcb.c       |   2 +-
 drivers/net/hns3/hns3_ethdev.c    | 116 ++++++++++++++++++++++++++++++--------
 drivers/net/hns3/hns3_ethdev.h    |   4 +-
 drivers/net/hns3/hns3_ethdev_vf.c |  62 ++++++++++++++------
 drivers/net/hns3/hns3_flow.c      |  36 ++++++------
 drivers/net/hns3/hns3_intr.c      |  22 +++++---
 drivers/net/hns3/hns3_mbx.c       |   4 +-
 drivers/net/hns3/hns3_rss.c       |  28 ++++-----
 drivers/net/hns3/hns3_rss.h       |   5 +-
 drivers/net/hns3/hns3_stats.c     |  21 +++++--
 drivers/net/hns3/hns3_tm.c        |   6 ++
 13 files changed, 258 insertions(+), 102 deletions(-)

-- 
2.7.4


             reply	other threads:[~2021-02-03 12:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 12:23 Lijun Ou [this message]
2021-02-03 12:23 ` [dpdk-dev] [PATCH 01/11] net/hns3: fix query order of link status and link info Lijun Ou
2021-02-03 12:23 ` [dpdk-dev] [PATCH 02/11] net/hns3: fix link status change from firmware Lijun Ou
2021-02-03 12:23 ` [dpdk-dev] [PATCH 03/11] net/hns3: fix RSS indirection table size Lijun Ou
2021-02-03 12:23 ` [dpdk-dev] [PATCH 04/11] net/hns3: constraint TM peak rate Lijun Ou
2021-02-03 12:23 ` [dpdk-dev] [PATCH 05/11] net/hns3: remove MPLS type from supported flow items Lijun Ou
2021-02-03 12:23 ` [dpdk-dev] [PATCH 06/11] net/hns3: fix stats flip overflow Lijun Ou
2021-02-03 12:23 ` [dpdk-dev] [PATCH 07/11] net/hns3: replace all atomic type with C11 atomic builtins Lijun Ou
2021-02-03 12:23 ` [dpdk-dev] [PATCH 08/11] net/hns3: fix FD rule residue in hardware when malloc fail Lijun Ou
2021-02-03 12:23 ` [dpdk-dev] [PATCH 09/11] net/hns3: fix cmdq cleared during firmware process Lijun Ou
2021-02-03 12:23 ` [dpdk-dev] [PATCH 10/11] net/hns3: fix VF reset after MBX failed Lijun Ou
2021-02-03 12:23 ` [dpdk-dev] [PATCH 11/11] net/hns3: add check for max pkt length of Rx Lijun Ou
2021-02-04 15:45 ` [dpdk-dev] [PATCH 00/11] critical bugfixes for hns3 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=1612355037-48768-1-git-send-email-oulijun@huawei.com \
    --to=oulijun@huawei.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=linuxarm@openeuler.org \
    /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).