From: Suanming Mou <suanmingm@nvidia.com>
To: viacheslavo@nvidia.com, matan@nvidia.com
Cc: rasland@nvidia.com, dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/4] net/mlx: fix secondary process bugs
Date: Sun, 24 Jan 2021 19:02:02 +0800 [thread overview]
Message-ID: <1611486126-84749-1-git-send-email-suanmingm@nvidia.com> (raw)
This patch series fix several secondary process bugs.
Suanming Mou (4):
net/mlx5: fix invalid multi-process ID
net/mlx5: fix secondary process port detach crash
net/mlx5: fix secondary process attach port Tx queue
net/mlx4: fix secondary process attach port Tx queue
drivers/net/mlx4/mlx4.c | 10 +++++-----
drivers/net/mlx4/mlx4.h | 4 ++++
drivers/net/mlx4/mlx4_mp.c | 24 ++++++++++++++++++++++++
drivers/net/mlx4/mlx4_rxtx.h | 1 +
drivers/net/mlx4/mlx4_txq.c | 28 ++++++++++++++++++++++++++++
drivers/net/mlx5/linux/mlx5_mp_os.c | 19 +++++++++++++++++++
drivers/net/mlx5/linux/mlx5_os.c | 4 ++--
drivers/net/mlx5/mlx5.c | 8 ++++----
drivers/net/mlx5/mlx5.h | 6 +++++-
drivers/net/mlx5/mlx5_txq.c | 21 +++++++++++++--------
10 files changed, 105 insertions(+), 20 deletions(-)
--
1.8.3.1
next reply other threads:[~2021-01-24 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 11:02 Suanming Mou [this message]
2021-01-24 11:02 ` [dpdk-dev] [PATCH 1/4] net/mlx5: fix invalid multi-process ID Suanming Mou
2021-01-25 8:31 ` Raslan Darawsheh
2021-01-24 11:02 ` [dpdk-dev] [PATCH 2/4] net/mlx5: fix secondary process port detach crash Suanming Mou
2021-01-24 11:02 ` [dpdk-dev] [PATCH 3/4] net/mlx5: fix secondary process attach port Tx queue Suanming Mou
2021-01-25 8:30 ` Raslan Darawsheh
2021-01-24 11:02 ` [dpdk-dev] [PATCH 4/4] net/mlx4: " Suanming Mou
2021-01-25 10:09 ` [dpdk-dev] [PATCH 0/4] net/mlx: fix secondary process bugs 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=1611486126-84749-1-git-send-email-suanmingm@nvidia.com \
--to=suanmingm@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=viacheslavo@nvidia.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).