From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: [PATCH RFC 2/2] RDMA/nldev: provide detailed CM_ID information Date: Tue, 6 Feb 2018 08:25:15 -0700 Message-ID: <20180206152515.GD10095@ziepe.ca> References: <20180204150553.GH27780@mtr-leonro.local> <015301d39e96$9f5e0b60$de1a2220$@opengridcomputing.com> <20180205200020.GH11446@mellanox.com> <026201d39ebf$d1f087a0$75d196e0$@opengridcomputing.com> <20180205203608.GJ11446@mellanox.com> <026a01d39ec3$5cc48270$164d8750$@opengridcomputing.com> <20180205211618.GL11446@mellanox.com> <026c01d39ece$fd9cf550$f8d6dff0$@opengridcomputing.com> <20180205222025.GC10095@ziepe.ca> <20180206084019.GL2567@mtr-leonro.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20180206084019.GL2567-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Leon Romanovsky Cc: Steve Wise , dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-rdma@vger.kernel.org On Tue, Feb 06, 2018 at 10:40:19AM +0200, Leon Romanovsky wrote: > On Mon, Feb 05, 2018 at 03:20:25PM -0700, Jason Gunthorpe wrote: > > On Mon, Feb 05, 2018 at 04:16:37PM -0600, Steve Wise wrote: > > > > > > > > On Mon, Feb 05, 2018 at 02:53:23PM -0600, Steve Wise wrote: > > > > > > > > > Even if we create a device-unique ID for each restrack object, to make > > > it > > > > > useful to for userspace analysis would require exposing that ID in the > > > > > various user object structures (or via query methods). EG having > > > > > pd->res_id, cq->res_id, etc... > > > > > > > > As I said, we have that, it is the fd, handle # tuple and most verbs > > > > objects expose the handle # in the user visible part of the object > > > > struct.. > > > > > > Can you please show me an example of the handle # for some object like PD or > > > CQ? > > > > From rdma-core verbs.h: > > > > struct ibv_pd { > > struct ibv_context *context; > > uint32_t handle; > > }; > > > > > This doesn't address kernel users' object, though, correct? > > > > Right. > > > > And id'ing a file descriptor gets kinda hard too.. > > And how should we handle kernel objects? hash'd pointer to internal struct? Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html