From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Ariel Levkovich <lariel@mellanox.com>,
Eli Cohen <eli@mellanox.com>, Mark Bloch <markb@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH rdma-next 4/8] IB/mlx5: Add steering SW ICM device memory type
Date: Wed, 24 Apr 2019 10:04:40 -0300 [thread overview]
Message-ID: <20190424130440.GA5196@ziepe.ca> (raw)
In-Reply-To: <20190331164450.23618-5-leon@kernel.org>
On Sun, Mar 31, 2019 at 07:44:46PM +0300, Leon Romanovsky wrote:
> From: Ariel Levkovich <lariel@mellanox.com>
>
> This patch adds support for allocating, deallocating and registering
> a new device memory type, STEERING_SW_ICM.
> This memory can be allocated and used by a privileged user for direct
> rule insertion and management of the device's steering tables.
>
> The type is provided by the user via the dedicated attribute in
> the alloc_dm ioctl command.
>
> Signed-off-by: Ariel Levkovich <lariel@mellanox.com>
> Reviewed-by: Eli Cohen <eli@mellanox.com>
> Reviewed-by: Mark Bloch <markb@mellanox.com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> drivers/infiniband/hw/mlx5/Kconfig | 2 +-
> drivers/infiniband/hw/mlx5/cmd.c | 127 +++++++++++++++++++-
> drivers/infiniband/hw/mlx5/cmd.h | 6 +-
> drivers/infiniband/hw/mlx5/main.c | 136 +++++++++++++++++++++-
> drivers/infiniband/hw/mlx5/mlx5_ib.h | 17 +++
> drivers/infiniband/hw/mlx5/mr.c | 7 ++
> include/uapi/rdma/mlx5_user_ioctl_verbs.h | 2 +
> 7 files changed, 291 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/infiniband/hw/mlx5/Kconfig b/drivers/infiniband/hw/mlx5/Kconfig
> index 8d651c05de62..347d457fcb2f 100644
> +++ b/drivers/infiniband/hw/mlx5/Kconfig
> @@ -1,6 +1,6 @@
> config MLX5_INFINIBAND
> tristate "Mellanox 5th generation network adapters (ConnectX series) support"
> - depends on NETDEVICES && ETHERNET && PCI && MLX5_CORE
> + depends on NETDEVICES && ETHERNET && PCI && MLX5_CORE && PHYS_ADDR_T_64BIT
Why do we need this?
Jason
next prev parent reply other threads:[~2019-04-24 13:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 16:44 [PATCH rdma-next 0/8] User space steering Leon Romanovsky
2019-03-31 16:44 ` [PATCH mlx5-next 1/8] net/mlx5: Expose SW ICM related device memory capabilities Leon Romanovsky
2019-03-31 16:44 ` [PATCH rdma-next 2/8] IB/mlx5: Support device memory type attribute Leon Romanovsky
2019-03-31 16:44 ` [PATCH rdma-next 3/8] IB/mlx5: Warn on allocated MEMIC buffers during cleanup Leon Romanovsky
2019-03-31 16:44 ` [PATCH rdma-next 4/8] IB/mlx5: Add steering SW ICM device memory type Leon Romanovsky
2019-04-24 13:04 ` Jason Gunthorpe [this message]
2019-04-24 13:12 ` Leon Romanovsky
2019-04-24 13:14 ` Jason Gunthorpe
2019-04-24 13:25 ` Leon Romanovsky
2019-04-24 13:35 ` Jason Gunthorpe
2019-04-24 13:46 ` Leon Romanovsky
2019-04-24 13:47 ` Jason Gunthorpe
2019-04-24 15:49 ` Leon Romanovsky
2019-04-24 15:53 ` Jason Gunthorpe
2019-04-24 16:27 ` Leon Romanovsky
2019-04-24 16:39 ` Jason Gunthorpe
2019-04-28 11:38 ` Leon Romanovsky
2019-04-28 11:56 ` Jason Gunthorpe
2019-03-31 16:44 ` [PATCH rdma-next 5/8] IB/mlx5: Device resource control for privileged DEVX user Leon Romanovsky
2019-03-31 16:44 ` [PATCH mlx5-next 6/8] net/mlx5: Expose TIR ICM address in command outbox Leon Romanovsky
2019-03-31 16:44 ` [PATCH mlx5-next 7/8] net/mlx5: Introduce new TIR creation core API Leon Romanovsky
2019-03-31 16:44 ` [PATCH rdma-next 8/8] IB/mlx5: Expose TIR ICM address to user space Leon Romanovsky
2019-03-31 21:06 ` [PATCH rdma-next 0/8] User space steering Jakub Kicinski
2019-04-01 6:28 ` Leon Romanovsky
2019-04-01 18:32 ` Jakub Kicinski
2019-04-02 8:14 ` Leon Romanovsky
2019-04-02 17:10 ` Jakub Kicinski
2019-04-24 13:07 ` Jason Gunthorpe
2019-04-24 16:40 ` Saeed Mahameed
2019-04-24 19:03 ` Jason Gunthorpe
2019-04-24 19:41 ` Saeed Mahameed
2019-04-25 13:34 ` 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=20190424130440.GA5196@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=eli@mellanox.com \
--cc=lariel@mellanox.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=markb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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).