From: Ophir Munk <ophirmu@mellanox.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Olga Shern <olgas@mellanox.com>, Matan Azrad <matan@mellanox.com>,
Ophir Munk <ophirmu@mellanox.com>
Subject: [dpdk-dev] [PATCH v1 0/7] net/mlx4: follow-up on new TX datapath introduced in RC1
Date: Mon, 23 Oct 2017 10:04:20 +0000 [thread overview]
Message-ID: <1508753067-30643-1-git-send-email-ophirmu@mellanox.com> (raw)
v1:
This series is a follow-up of the new datapath implementation introduced in RC1.
It is dedicated to Tx and improves the performance.
Matan Azrad (4):
net/mlx4: remove error flows from Tx fast path
net/mlx4: merge Tx path functions
net/mlx4: remove unnecessary variables in Tx burst
net/mlx4: improve performance of one Tx segment
Ophir Munk (3):
net/mlx4: inline more Tx functions
net/mlx4: save lkey in big-endian format
net/mlx4: separate Tx for multi-segments
drivers/net/mlx4/mlx4_rxtx.c | 345 +++++++++++++++++++++++--------------------
drivers/net/mlx4/mlx4_rxtx.h | 56 ++++++-
2 files changed, 235 insertions(+), 166 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-23 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 10:04 Ophir Munk [this message]
2017-10-23 10:04 ` [dpdk-dev] [PATCH v1 1/7] net/mlx4: remove error flows from Tx fast path Ophir Munk
2017-10-23 10:04 ` [dpdk-dev] [PATCH v1 2/7] net/mlx4: inline more Tx functions Ophir Munk
2017-10-23 10:04 ` [dpdk-dev] [PATCH v1 3/7] net/mlx4: save lkey in big-endian format Ophir Munk
2017-10-23 10:04 ` [dpdk-dev] [PATCH v1 4/7] net/mlx4: merge Tx path functions Ophir Munk
2017-10-23 10:04 ` [dpdk-dev] [PATCH v1 5/7] net/mlx4: remove unnecessary variables in Tx burst Ophir Munk
2017-10-23 10:04 ` [dpdk-dev] [PATCH v1 6/7] net/mlx4: improve performance of one Tx segment Ophir Munk
2017-10-23 10:04 ` [dpdk-dev] [PATCH v1 7/7] net/mlx4: separate Tx for multi-segments Ophir Munk
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=1508753067-30643-1-git-send-email-ophirmu@mellanox.com \
--to=ophirmu@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=olgas@mellanox.com \
--cc=thomas@monjalon.net \
/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).