From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 00/14] Fixes for mlx4 and mlx5
Date: Mon, 23 Nov 2015 15:44:35 +0100 [thread overview]
Message-ID: <1448289889-9590-1-git-send-email-adrien.mazarguil@6wind.com> (raw)
Here is a set of fixes for mlx4 and mlx5. Since mlx5 derives from mlx4,
most patches apply to both PMDs.
Besides bugfixes, there is a documentation commit for mlx5 (undocumented
environment variables) and another commit that addresses secondary process
operation with mlx4 (does not work at all).
Adrien Mazarguil (6):
mlx4: fix possible crash when clearing device statistics
mlx4: fix memory registration for indirect mbuf data
mlx4: fix TX for scattered mbufs with too many segments
mlx5: fix possible crash when clearing device statistics
mlx5: fix memory registration for indirect mbuf data
mlx5: fix TX for scattered mbufs with too many segments
Nelio Laranjeiro (2):
mlx4: fix available entries in TX rings
mlx5: fix available entries in TX rings
Olga Shern (5):
mlx4: fix TX packet loss after initialization
mlx4: fix local protection error when TX MP to MR cache is full
mlx5: fix TX packet loss after initialization
mlx5: fix local protection error when TX MP to MR cache is full
mlx5: add environment variables section to documentation
Or Ami (1):
mlx4: allow operation in secondary processes
doc/guides/nics/mlx5.rst | 13 ++
drivers/net/mlx4/mlx4.c | 503 ++++++++++++++++++++++++++++++++++++++++--
drivers/net/mlx5/mlx5_rxtx.c | 114 +++++++++-
drivers/net/mlx5/mlx5_rxtx.h | 3 +-
drivers/net/mlx5/mlx5_stats.c | 2 +-
drivers/net/mlx5/mlx5_txq.c | 2 +
6 files changed, 603 insertions(+), 34 deletions(-)
--
2.1.0
next reply other threads:[~2015-11-23 14:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 14:44 Adrien Mazarguil [this message]
2015-11-23 14:44 ` [dpdk-dev] [PATCH 01/14] mlx4: fix possible crash when clearing device statistics Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 02/14] mlx4: fix memory registration for indirect mbuf data Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 03/14] mlx4: fix TX for scattered mbufs with too many segments Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 04/14] mlx4: fix TX packet loss after initialization Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 05/14] mlx4: fix local protection error when TX MP to MR cache is full Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 06/14] mlx4: fix available entries in TX rings Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 07/14] mlx4: allow operation in secondary processes Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 08/14] mlx5: fix possible crash when clearing device statistics Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 09/14] mlx5: fix memory registration for indirect mbuf data Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 10/14] mlx5: fix TX for scattered mbufs with too many segments Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 11/14] mlx5: fix TX packet loss after initialization Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 12/14] mlx5: fix local protection error when TX MP to MR cache is full Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 13/14] mlx5: fix available entries in TX rings Adrien Mazarguil
2015-11-23 14:44 ` [dpdk-dev] [PATCH 14/14] mlx5: add environment variables section to documentation Adrien Mazarguil
2015-11-24 16:32 ` [dpdk-dev] [PATCH 00/14] Fixes for mlx4 and mlx5 Thomas Monjalon
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=1448289889-9590-1-git-send-email-adrien.mazarguil@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
/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).