DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@mellanox.com>
To: Matan Azrad <matan@mellanox.com>, Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 0/3] improve failsafe performance
Date: Tue, 19 Dec 2017 17:21:28 +0000	[thread overview]
Message-ID: <HE1PR0502MB36597CD5D4E0D4B236142197D20F0@HE1PR0502MB3659.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1513703669-29363-1-git-send-email-matan@mellanox.com>

All this series patches are V1.
Sorry for V3 mistake.

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Matan Azrad
> Sent: Tuesday, December 19, 2017 7:14 PM
> To: Gaetan Rivet <gaetan.rivet@6wind.com>
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v3 0/3] improve failsafe performance
> 
> This fail-safe series should improve some cycles in failsafe data path.
> It is obvious that we cannot improve a lot because the most of data path
> functionality are done by the sub devices data path.
> So the expectation from this series is just to improve some cycles in sub
> devices management done by fail-safe PMD.
> I saw ~1.7% MPPS improvement for 1 core 1 queue io-forwarding mode - 2
> sub-devices(mlx4 primary).
> 
> Matan Azrad (3):
>   net/failsafe: fix Rx safe check compiler hint
>   net/failsafe: mitigate data plan atomic operations
>   net/failsafe: improve Rx sub-devices iteration
> 
>  drivers/net/failsafe/failsafe.c         |  5 ++++
>  drivers/net/failsafe/failsafe_ops.c     |  1 +
>  drivers/net/failsafe/failsafe_private.h |  9 +++---
>  drivers/net/failsafe/failsafe_rxtx.c    | 50 ++++++++++-----------------------
>  4 files changed, 26 insertions(+), 39 deletions(-)
> 
> --
> 1.8.3.1

  parent reply	other threads:[~2017-12-19 17:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 17:14 Matan Azrad
2017-12-19 17:14 ` [dpdk-dev] [PATCH v3 1/3] net/failsafe: fix Rx safe check compiler hint Matan Azrad
2017-12-19 17:14 ` [dpdk-dev] [PATCH v3 2/3] net/failsafe: mitigate data plan atomic operations Matan Azrad
2017-12-19 17:14 ` [dpdk-dev] [PATCH v3 3/3] net/failsafe: improve Rx sub-devices iteration Matan Azrad
2018-01-12 10:28   ` Gaëtan Rivet
2018-01-12 13:29     ` Matan Azrad
2018-01-12 14:01       ` Gaëtan Rivet
2017-12-19 17:21 ` Matan Azrad [this message]
2018-01-11 17:58 ` [dpdk-dev] [PATCH v3 0/3] improve failsafe performance Ferruh Yigit
2018-01-12 10:14   ` Gaëtan Rivet
2018-01-12 15:10 ` 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=HE1PR0502MB36597CD5D4E0D4B236142197D20F0@HE1PR0502MB3659.eurprd05.prod.outlook.com \
    --to=matan@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@6wind.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).