From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Matan Azrad <matan@mellanox.com>, Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/3] improve failsafe performance
Date: Fri, 12 Jan 2018 15:10:40 +0000 [thread overview]
Message-ID: <a67c5786-8ebe-fec2-7875-690ba1a5ed18@intel.com> (raw)
In-Reply-To: <1513703669-29363-1-git-send-email-matan@mellanox.com>
On 12/19/2017 5:14 PM, Matan Azrad wrote:
> 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
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-01-12 15:10 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 ` [dpdk-dev] [PATCH v3 0/3] improve failsafe performance Matan Azrad
2018-01-11 17:58 ` Ferruh Yigit
2018-01-12 10:14 ` Gaëtan Rivet
2018-01-12 15:10 ` Ferruh Yigit [this message]
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=a67c5786-8ebe-fec2-7875-690ba1a5ed18@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
--cc=matan@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).