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>,
Guy Levi <guyle@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>,
Yonatan Cohen <yonatanc@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH rdma-next 3/3] IB/mlx5: Expose dump and fill memory key
Date: Wed, 4 Jul 2018 13:09:37 -0600 [thread overview]
Message-ID: <20180704190937.GA15732@ziepe.ca> (raw)
In-Reply-To: <20180619054724.32677-4-leon@kernel.org>
On Tue, Jun 19, 2018 at 08:47:24AM +0300, Leon Romanovsky wrote:
> From: Yonatan Cohen <yonatanc@mellanox.com>
>
> MLX5 IB HCA offers the memory key, dump_fill_mkey to boost
> performance, when used in a send or receive operations.
>
> It is used to force local HCA operations to skip the PCI bus access,
> while keeping track of the processed length in the ibv_sge handling.
>
> Meaning, instead of a PCI write access the HCA leaves the target
> memory untouched, and skips filling that packet section. Similar
> behavior is done upon send, the HCA skips data in memory relevant
> to this key and saves PCI bus access.
>
> This functionality saves PCI read/write operations.
>
> Signed-off-by: Yonatan Cohen <yonatanc@mellanox.com>
> Reviewed-by: Yishai Hadas <yishaih@mellanox.com>
> Reviewed-by: Guy Levi <guyle@mellanox.com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> drivers/infiniband/hw/mlx5/main.c | 16 +++++++++++++++-
> include/uapi/rdma/mlx5-abi.h | 3 ++-
> 2 files changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/infiniband/hw/mlx5/main.c b/drivers/infiniband/hw/mlx5/main.c
> index c29c7c838980..97113957398d 100644
> +++ b/drivers/infiniband/hw/mlx5/main.c
> @@ -1634,6 +1634,7 @@ static struct ib_ucontext *mlx5_ib_alloc_ucontext(struct ib_device *ibdev,
> int err;
> size_t min_req_v2 = offsetof(struct mlx5_ib_alloc_ucontext_req_v2,
> max_cqe_version);
> + u32 dump_fill_mkey;
> bool lib_uar_4k;
>
> if (!dev->ib_active)
> @@ -1743,8 +1744,12 @@ static struct ib_ucontext *mlx5_ib_alloc_ucontext(struct ib_device *ibdev,
> }
>
> err = mlx5_ib_devx_create(dev, context);
> + }
> +
> + if (MLX5_CAP_GEN(dev->mdev, dump_fill_mkey)) {
> + err = mlx5_cmd_dump_fill_mkey(dev->mdev, &dump_fill_mkey);
> if (err)
> - goto out_td;
> + goto out_mdev;
> }
Dropping the if (err) after mlx5_ib_devx_create is a rebasing error,
right?
Jason
next prev parent reply other threads:[~2018-07-04 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 5:47 [PATCH rdma-next 0/3] Dump and fill MKEY Leon Romanovsky
2018-06-19 5:47 ` [PATCH mlx5-next 1/3] net/mlx5: Limit scope of dump_fill_mkey function Leon Romanovsky
2018-06-19 5:47 ` [PATCH mlx5-next 2/3] net/mlx5: Add hardware definitions for dump_fill_mkey Leon Romanovsky
2018-06-19 5:47 ` [PATCH rdma-next 3/3] IB/mlx5: Expose dump and fill memory key Leon Romanovsky
2018-07-04 19:09 ` Jason Gunthorpe [this message]
2018-07-04 19:20 ` Leon Romanovsky
2018-06-19 14:21 ` [PATCH rdma-next 0/3] Dump and fill MKEY Jason Gunthorpe
2018-06-19 14:26 ` Leon Romanovsky
2018-07-04 17:47 ` Jason Gunthorpe
2018-07-04 18:54 ` Leon Romanovsky
2018-07-04 19:29 ` 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=20180704190937.GA15732@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=guyle@mellanox.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=yishaih@mellanox.com \
--cc=yonatanc@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).