From: Matan Azrad <matan@mellanox.com>
To: Kevin Traynor <ktraynor@redhat.com>,
Shahaf Shuler <shahafs@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1 0/9] mlx5: Handle data-path completions with error
Date: Sun, 22 Sep 2019 07:03:21 +0000 [thread overview]
Message-ID: <AM0PR0502MB40193D496ABB3627D3F12479D28A0@AM0PR0502MB4019.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <81aa0ce1-14c0-1e95-0caa-5a4607317600@redhat.com>
From: Kevin Traynor
> On 30/05/2019 11:20, Matan Azrad wrote:
> > 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(-)
> >
>
>
> Hi - these changes are very invasive ^^^. I'm not really comfortable to take
> this for 18.11.3. See
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.d
> pdk.org%2Fguides%2Fcontributing%2Fstable.html%23what-changes-should-
> be-
> backported&data=02%7C01%7Cmatan%40mellanox.com%7Cf8c9305dc6
> 7b4e7b128008d7377ad4f9%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C
> 0%7C637038873031127944&sdata=HAm39aLCoHz59wauVmglWrq5fwnM
> 3ZtLV0%2FebrZHiLY%3D&reserved=0
>
> I will take patch 3/9 as it is a fix with Fixes: tag.
It's ok, the others are not must in this version.
>
> thanks,
> Kevin.
next prev parent reply other threads:[~2019-09-22 7:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 10:20 Matan Azrad
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 [this message]
[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=AM0PR0502MB40193D496ABB3627D3F12479D28A0@AM0PR0502MB4019.eurprd05.prod.outlook.com \
--to=matan@mellanox.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=shahafs@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).