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,
Maor Gottlieb <maorg@mellanox.com>
Subject: [PATCH rdma-next 0/6] Cleanup mlx5_ib main file
Date: Thu, 2 Jul 2020 11:18:03 +0300 [thread overview]
Message-ID: <20200702081809.423482-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@mellanox.com>
Over the years, the main.c file grew above all imagination and was >8K
LOC of the code. This caused to a huge burden while I started to work on
ib_flow allocation patches.
This series implements long standing "internal" wish to move flow logic
from the main to separate file.
Based on
https://lore.kernel.org/linux-rdma/20200630101855.368895-4-leon@kernel.org
Thanks
Leon Romanovsky (6):
RDMA/mlx5: Limit the scope of mlx5_ib_enable_driver function
RDMA/mlx5: Separate restrack callbacks initialization from main.c
RDMA/mlx5: Separate counters from main.c
RDMA/mlx5: Separate flow steering logic from main.c
RDMA/mlx5: Cleanup DEVX initialization flow
RDMA/mlx5: Delete one-time used functions
drivers/infiniband/hw/mlx5/Makefile | 3 +-
drivers/infiniband/hw/mlx5/cmd.c | 12 -
drivers/infiniband/hw/mlx5/cmd.h | 1 -
drivers/infiniband/hw/mlx5/counters.c | 709 +++++
drivers/infiniband/hw/mlx5/counters.h | 17 +
drivers/infiniband/hw/mlx5/devx.c | 102 +-
drivers/infiniband/hw/mlx5/devx.h | 45 +
drivers/infiniband/hw/mlx5/flow.c | 765 -----
drivers/infiniband/hw/mlx5/fs.c | 2514 +++++++++++++++
drivers/infiniband/hw/mlx5/fs.h | 29 +
drivers/infiniband/hw/mlx5/main.c | 4112 +++++--------------------
drivers/infiniband/hw/mlx5/mlx5_ib.h | 76 +-
drivers/infiniband/hw/mlx5/qp.c | 1 +
drivers/infiniband/hw/mlx5/qp.h | 1 +
drivers/infiniband/hw/mlx5/restrack.c | 29 +-
drivers/infiniband/hw/mlx5/restrack.h | 13 +
16 files changed, 4184 insertions(+), 4245 deletions(-)
create mode 100644 drivers/infiniband/hw/mlx5/counters.c
create mode 100644 drivers/infiniband/hw/mlx5/counters.h
create mode 100644 drivers/infiniband/hw/mlx5/devx.h
delete mode 100644 drivers/infiniband/hw/mlx5/flow.c
create mode 100644 drivers/infiniband/hw/mlx5/fs.c
create mode 100644 drivers/infiniband/hw/mlx5/fs.h
create mode 100644 drivers/infiniband/hw/mlx5/restrack.h
--
2.26.2
next reply other threads:[~2020-07-02 8:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 8:18 Leon Romanovsky [this message]
2020-07-02 8:18 ` [PATCH rdma-next 1/6] RDMA/mlx5: Limit the scope of mlx5_ib_enable_driver function Leon Romanovsky
2020-07-02 8:18 ` [PATCH rdma-next 2/6] RDMA/mlx5: Separate restrack callbacks initialization from main.c Leon Romanovsky
2020-07-02 8:18 ` [PATCH rdma-next 3/6] RDMA/mlx5: Separate counters " Leon Romanovsky
2020-07-02 8:18 ` [PATCH rdma-next 4/6] RDMA/mlx5: Separate flow steering logic " Leon Romanovsky
2020-07-02 8:18 ` [PATCH rdma-next 5/6] RDMA/mlx5: Cleanup DEVX initialization flow Leon Romanovsky
2020-07-02 8:18 ` [PATCH rdma-next 6/6] RDMA/mlx5: Delete one-time used functions Leon Romanovsky
2020-07-02 13:08 ` [PATCH rdma-next 0/6] Cleanup mlx5_ib main file Jason Gunthorpe
2020-07-02 13:11 ` Leon Romanovsky
2020-07-07 17:42 ` 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=20200702081809.423482-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=maorg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.