>Hum.. Not sure how that would work? src = AF_INET, dst = AF_IB? yes - conceptually, these both map to PF_IB, which I think is really the limiting factor
I'm guessing that you could make the reverse work as well, but it requires more work and probably wouldn't be used by apps anyway. >I guess I was hoping you'd be able to do the private data in userspace >and avoid those kind of special cases.. The private data would still be done in user space. This allows apps that make use of ADDR_CHANGE events to continue working as normal, while still allowing for address resolution to be done in user space. This should meet Or's request. User space may not know if they can resolve a particular address before binding. I need to write the kernel patches to see if supporting this causes undo grief. At this point, I'm guessing that the only thing that would prevent this from working is if an explicit check is added. - Sean -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
