Re: [PATCH V3 5/6] RDMA CM: Save Owning PID

[Nir Muchtar <nirm-smomgflXvOZWk0Htik3J/w@public.gmane.org>]

On Tue, 2010-12-21 at 13:36 -0700, Jason Gunthorpe wrote:

> The question is how do your correlate the kernel ID with the userspace
> process(es) that have ownership of it. The only way to do that is to
> associate the ID with the event channel FD with the process(es) that
> have access to it.
> 
> Unfortunately there is no other way to correlate the in-kernel ID with
> the process(es) that control it.
> 
> Jason

Ok, seems like we're going in circles...
The fact is that there is a way, that, all arguments aside, just works,
and IMO is coherent with the current way that RDMA CM IDs are managed.

Right now this is also the only practical way to export this
information, because RDMA CM/UCM don't behave like sock does in terms of
inode information. 

Also, in practice, many RDMA CM IDs are, in fact, created by the kernel
(when new connections are established), so I'm not sure if what you're
suggesting is even feasible with the current design of RDMA CM.

I realize you disagree, but I still want to move forward with the rest,
so I'll separate this patch from the rest and we can have a separate
discussion over this in the future.

Nir

--
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