Re: [PATCH v5 00/16] Add Paravirtual RDMA Driver

2 messages, 2 authors, 2016-09-26 · open the first message on its own page

Re: [PATCH v5 00/16] Add Paravirtual RDMA Driver

From: Jason Gunthorpe <hidden>
Date: 2016-09-26 16:51:04

On Sun, Sep 25, 2016 at 10:25:12PM -0700, Adit Ranadive wrote:
quoted
As Jason said, you need a very good reason to split and create number of
files per-driver in UAPI folder.
I can move the pvrdma-uapi.h back to the pvrdma driver folder.
Just don't copy any of the content into your user space provider.

Thanks
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

Re: [PATCH v5 00/16] Add Paravirtual RDMA Driver

From: Adit Ranadive <hidden>
Date: 2016-09-26 20:44:14

On Mon, Sep 26, 2016 at 10:51:04AM -0600, Jason Gunthorpe wrote:
On Sun, Sep 25, 2016 at 10:25:12PM -0700, Adit Ranadive wrote:
quoted
quoted
As Jason said, you need a very good reason to split and create number of
files per-driver in UAPI folder.
I can move the pvrdma-uapi.h back to the pvrdma driver folder.
Just don't copy any of the content into your user space provider.
Thanks. I wanted to clarify regarding device specific structures since that
is what our pvrdma-uapi.h file has.

Wouldnt they be some overlap between the user-space and kernel driver? Or is
it expected that the common structures (even device specific ones) be moved to
the ABI file?

For the mlx4 driver I see that the structures in include/linux/mlx4/qp.h
and in libmlx4/src/wqe.h are similar.

Thanks,
Adit
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help