Netdev Archive on lore.kernel.org help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com> To: Leon Romanovsky <leon@kernel.org> Cc: Doug Ledford <dledford@redhat.com>, Aharon Landau <aharonl@nvidia.com>, Jakub Kicinski <kuba@kernel.org>, Jason Wang <jasowang@redhat.com>, linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>, netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>, Shay Drory <shayd@nvidia.com>, virtualization@lists.linux-foundation.org Subject: Re: [PATCH mlx5-next 2/5] RDMA/mlx5: Move struct mlx5_core_mkey to mlx5_ib Date: Thu, 29 Jul 2021 15:39:52 -0300 [thread overview] Message-ID: <20210729183952.GA2408484@nvidia.com> (raw) In-Reply-To: <db1e0478b61de2a051be2454065d41fd6c27a0d8.1624362290.git.leonro@nvidia.com> On Tue, Jun 22, 2021 at 03:08:20PM +0300, Leon Romanovsky wrote: > diff --git a/drivers/infiniband/hw/mlx5/mlx5_ib.h b/drivers/infiniband/hw/mlx5/mlx5_ib.h > index 7bb35a3d8004..af11a0d8ebc0 100644 > +++ b/drivers/infiniband/hw/mlx5/mlx5_ib.h > @@ -634,9 +634,19 @@ struct mlx5_user_mmap_entry { > #define mlx5_update_odp_stats(mr, counter_name, value) \ > atomic64_add(value, &((mr)->odp_stats.counter_name)) > > +struct mlx5r_mkey { Not mlx5_ib_mkey? mlx5_ib_odp_mkey might capture the intention of what this is actually for. > + u64 iova; IOVA is already stored in ib_mr->iova, no need to duplicate it here. > + u64 size; Only one place reads size in mlx5_ib_create_xlt_wr(), and it can be mr->ibmr.length, so delete size > + u32 key; > + u32 pd; Lots of places write to this but nothing reads it, delete it. > + u32 type; Please drop the horizontal spacing type should be a proper enum not u32 and the values should be moved out of driver.h as well. ndescs should probably be added here instead of in the containing structs since ODP needs it generically. This patch and the one before are a good cleanup on their own so they can get applied when they are fixed up enough. Each of the above changes to remove fields in the mlx5r_mkey struct should be single patches so this will little series will grow two more patches. Jason
next prev parent reply other threads:[~2021-07-29 18:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-22 12:08 [PATCH rdma-next 0/5] mlx5 MR cache enhancements Leon Romanovsky 2021-06-22 12:08 ` [PATCH mlx5-next 1/5] RDMA/mlx5: Replace struct mlx5_core_mkey by u32 key Leon Romanovsky 2021-07-29 15:28 ` Jason Gunthorpe 2021-07-29 17:27 ` Leon Romanovsky 2021-07-29 18:08 ` Jason Gunthorpe 2021-06-22 12:08 ` [PATCH mlx5-next 2/5] RDMA/mlx5: Move struct mlx5_core_mkey to mlx5_ib Leon Romanovsky 2021-07-29 18:39 ` Jason Gunthorpe [this message] 2021-06-22 12:08 ` [PATCH mlx5-next 3/5] RDMA/mlx5: Change the cache to hold mkeys instead of MRs Leon Romanovsky 2021-07-29 19:08 ` Jason Gunthorpe 2021-06-22 12:08 ` [PATCH mlx5-next 4/5] RDMA/mlx5: Change the cache structure to an rbtree Leon Romanovsky 2021-07-29 19:45 ` Jason Gunthorpe 2021-06-22 12:08 ` [PATCH rdma-next 5/5] RDMA/mlx5: Delay the deregistration of a non-cache mkey Leon Romanovsky
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=20210729183952.GA2408484@nvidia.com \ --to=jgg@nvidia.com \ --cc=aharonl@nvidia.com \ --cc=dledford@redhat.com \ --cc=jasowang@redhat.com \ --cc=kuba@kernel.org \ --cc=leon@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rdma@vger.kernel.org \ --cc=mst@redhat.com \ --cc=netdev@vger.kernel.org \ --cc=saeedm@nvidia.com \ --cc=shayd@nvidia.com \ --cc=virtualization@lists.linux-foundation.org \ /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: linkBe 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).