DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@mellanox.com>
To: Shahaf Shuler <shahafs@mellanox.com>, Yongseok Koh <yskoh@mellanox.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v1 0/9] mlx5: Handle data-path completions with error
Date: Thu, 30 May 2019 10:20:30 +0000	[thread overview]
Message-ID: <1559211639-17442-1-git-send-email-matan@mellanox.com> (raw)

Add support for data-path Rx and Tx completions with error handling:

1. Detect the error.
2. Do not crash.
3. Report it in statistics counters.
4. Dump debug information to system log file.
5. Recover the error under the hood.
6. Add support for secondary process recovery.

No performance impact was shown. 

Matan Azrad (9):
  net/mlx5: remove Rx queues indexes correlation
  net/mlx5: add log file procedure for debug data
  net/mlx5: fix device arguments error detection
  net/mlx5: mitigate Rx doorbell memory barrier
  net/mlx5: separate Rx queue initialization
  net/mlx5: extend Rx completion with error handling
  net/mlx5: handle Tx completion with error
  net/mlx5: recover secondary process Rx errors
  net/mlx5: recover secondary process Tx errors

 doc/guides/nics/mlx5.rst              |   7 +
 drivers/net/mlx5/mlx5.c               |  14 +-
 drivers/net/mlx5/mlx5.h               |  12 +
 drivers/net/mlx5/mlx5_mp.c            |  46 +++
 drivers/net/mlx5/mlx5_prm.h           |  11 +
 drivers/net/mlx5/mlx5_rxq.c           |  42 +--
 drivers/net/mlx5/mlx5_rxtx.c          | 673 ++++++++++++++++++++++++++++------
 drivers/net/mlx5/mlx5_rxtx.h          | 193 +++++-----
 drivers/net/mlx5/mlx5_rxtx_vec.c      |   5 +-
 drivers/net/mlx5/mlx5_rxtx_vec_neon.h |  36 +-
 drivers/net/mlx5/mlx5_rxtx_vec_sse.h  |  36 +-
 drivers/net/mlx5/mlx5_trigger.c       |   1 +
 drivers/net/mlx5/mlx5_txq.c           |   4 +-
 13 files changed, 792 insertions(+), 288 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2019-05-30 10:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 10:20 Matan Azrad [this message]
2019-05-30 10:20 ` [dpdk-dev] [PATCH v1 1/9] net/mlx5: remove Rx queues indexes correlation Matan Azrad
2019-05-30 10:20 ` [dpdk-dev] [PATCH v1 2/9] net/mlx5: add log file procedure for debug data Matan Azrad
2019-05-30 10:20 ` [dpdk-dev] [PATCH v1 3/9] net/mlx5: fix device arguments error detection Matan Azrad
2019-05-30 10:20 ` [dpdk-dev] [PATCH v1 4/9] net/mlx5: mitigate Rx doorbell memory barrier Matan Azrad
2019-05-30 10:20 ` [dpdk-dev] [PATCH v1 5/9] net/mlx5: separate Rx queue initialization Matan Azrad
2019-05-30 10:20 ` [dpdk-dev] [PATCH v1 6/9] net/mlx5: extend Rx completion with error handling Matan Azrad
2019-05-30 10:20 ` [dpdk-dev] [PATCH v1 7/9] net/mlx5: handle Tx completion with error Matan Azrad
2019-05-30 10:20 ` [dpdk-dev] [PATCH v1 8/9] net/mlx5: recover secondary process Rx errors Matan Azrad
2019-05-30 10:20 ` [dpdk-dev] [PATCH v1 9/9] net/mlx5: recover secondary process Tx errors Matan Azrad
2019-09-12 12:14 ` [dpdk-dev] [PATCH v1 0/9] mlx5: Handle data-path completions with error Kevin Traynor
2019-09-22  7:03   ` Matan Azrad
     [not found] <1559200565-15703-1-git-send-email-matan@mellanox.com>
2019-06-11 18:29 ` Shahaf Shuler

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=1559211639-17442-1-git-send-email-matan@mellanox.com \
    --to=matan@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=shahafs@mellanox.com \
    --cc=yskoh@mellanox.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).