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

2010-12-22 Thread Jason Gunthorpe
On Wed, Dec 22, 2010 at 06:03:33PM +0200, Nir Muchtar wrote: > 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. Are you referring to how proc/fd currently shows /dev/infiniband/rdma_cm for

[PATCH] Further timeout paramater verification (Was: [PATCH] infiniband-diags: Verify timeout value specified to diagnostics)

2010-12-22 Thread Ira Weiny
On Mon, 20 Dec 2010 13:57:36 -0800 Jay Fenlason wrote: > Sorry if you get this more than once, I seem to have outgoing mail > misconfiguration here. > > On Wed, Dec 15, 2010 at 11:47:09AM -0800, Ira Weiny wrote: > > > > Verify timeout value specified to diagnostics > > > > > > Signed-off-by: Ir

[PATCH] infiniband/mthca : Fix userland mapping of mthca infiniband cards in Xen dom0

2010-12-22 Thread Vivien Bernet-Rollande
Infiniband allows the mapping of PCI memory regions to userland to achieve faster speeds. Using this feature with mthca cards in a Xen dom0 kernel leads to a pretty bad crash, and the process being killed (see http://xen.1045712.n5.nabble.com/Infiniband-from-userland-in-dom0-process-killed-bad-pag

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

2010-12-22 Thread Nir Muchtar
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. > >