From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
To: dev@dpdk.org
Cc: yskoh@mellanox.com, shahafs@mellanox.com
Subject: [dpdk-dev] [PATCH 0/3] net/mlx5: transmit datapath cumulative fix pack
Date: Mon, 29 Jul 2019 12:41:02 +0000 [thread overview]
Message-ID: <1564404065-4823-1-git-send-email-viacheslavo@mellanox.com> (raw)
This series contains the pack of bug fixes and performance
improvements:
- limit the amount of freed buffers per one tx_burst call
- set the completion generating request in more uniform
fashion
- limit the number of packets in one descriptor to improve
latency
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Viacheslav Ovsiienko (3):
net/mlx5: fix Tx completion descriptors fetching loop
net/mlx5: fix ConnectX-4LX minimal inline data limit
net/mlx5: fix the Tx completion request generation
drivers/net/mlx5/mlx5.c | 7 +--
drivers/net/mlx5/mlx5_defs.h | 9 +++-
drivers/net/mlx5/mlx5_prm.h | 17 ++++---
drivers/net/mlx5/mlx5_rxtx.c | 110 +++++++++++++++++++++++++++++--------------
4 files changed, 97 insertions(+), 46 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-07-29 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 12:41 Viacheslav Ovsiienko [this message]
2019-07-29 12:41 ` [dpdk-dev] [PATCH 1/3] net/mlx5: fix Tx completion descriptors fetching loop Viacheslav Ovsiienko
2019-07-29 12:41 ` [dpdk-dev] [PATCH 2/3] net/mlx5: fix ConnectX-4LX minimal inline data limit Viacheslav Ovsiienko
2019-08-01 7:43 ` [dpdk-dev] [PATCH] net/mlx5: fix default minimal data inline Viacheslav Ovsiienko
2019-07-29 12:41 ` [dpdk-dev] [PATCH 3/3] net/mlx5: fix the Tx completion request generation Viacheslav Ovsiienko
2019-07-29 15:13 ` [dpdk-dev] [PATCH 0/3] net/mlx5: transmit datapath cumulative fix pack Matan Azrad
2019-07-29 15:23 ` Raslan Darawsheh
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=1564404065-4823-1-git-send-email-viacheslavo@mellanox.com \
--to=viacheslavo@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).