From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Max Gurtovoy <maxg@mellanox.com>
Subject: [PATCH rdma-next 0/3] mlx5 QP cleanup (cont.)
Date: Wed, 6 May 2020 09:55:10 +0300 [thread overview]
Message-ID: <20200506065513.4668-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@mellanox.com>
Hi,
This short series continue to cleanup qp.c file, which grew
to be completely unmaintainable.
Thanks
Leon Romanovsky (2):
RDMA/mlx5: Update mlx5_ib to use new cmd interface
RDMA/mlx5: Move all WR logic from qp.c to separate file
Max Gurtovoy (1):
RDMA/mlx5: Refactor mlx5_post_send() to improve readability
drivers/infiniband/hw/mlx5/Makefile | 3 +-
drivers/infiniband/hw/mlx5/cmd.c | 114 +-
drivers/infiniband/hw/mlx5/cmd.h | 4 +-
drivers/infiniband/hw/mlx5/cong.c | 4 +-
drivers/infiniband/hw/mlx5/main.c | 10 +-
drivers/infiniband/hw/mlx5/mlx5_ib.h | 4 -
drivers/infiniband/hw/mlx5/odp.c | 5 +-
drivers/infiniband/hw/mlx5/qp.c | 1488 +------------------------
drivers/infiniband/hw/mlx5/srq_cmd.c | 115 +-
drivers/infiniband/hw/mlx5/wr.c | 1504 ++++++++++++++++++++++++++
drivers/infiniband/hw/mlx5/wr.h | 76 ++
11 files changed, 1680 insertions(+), 1647 deletions(-)
create mode 100644 drivers/infiniband/hw/mlx5/wr.c
create mode 100644 drivers/infiniband/hw/mlx5/wr.h
--
2.26.2
next reply other threads:[~2020-05-06 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 6:55 Leon Romanovsky [this message]
2020-05-06 6:55 ` [PATCH rdma-next 1/3] RDMA/mlx5: Update mlx5_ib to use new cmd interface Leon Romanovsky
2020-05-06 6:55 ` [PATCH rdma-next 2/3] RDMA/mlx5: Refactor mlx5_post_send() to improve readability Leon Romanovsky
2020-05-06 6:55 ` [PATCH rdma-next 3/3] RDMA/mlx5: Move all WR logic from qp.c to separate file Leon Romanovsky
2020-05-06 20:45 ` [PATCH rdma-next 0/3] mlx5 QP cleanup (cont.) Jason Gunthorpe
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=20200506065513.4668-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maxg@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).