I think I have asked about this before, or at least tangentially in bug
1523.

The problem is, when I am building software against the OFED
kernel-ib-devel package, because the NFSRDMA headers are in the same
include tree as the OFED headers, I cannot get to the OFED headers and
avoid the NFSRDMA headers.

When is this a problem?  When I have built my OFED stack *without*
NFSRDMA support.

So my expectation is that the driver that I am building with the OFED
kernel-ib-devel will use the NFS and RPC implementation in the linux
kernel, not in /usr/src/ofa-kernel, however because the NFSRDMA
implementation is populated in the same include tree as the core OFED
implementation, I cannot avoid it.

Thots?
b.

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
ewg mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg

Reply via email to