> I hadn't looked at the kernel side yet; I was waiting for the userspace side > to > sort itself out first.
I think it makes sense to start with how user space can get the data. Without eating up reserved fields, we're starting with 8 bit values. > Hmm. 16 bits is probably enough for the MTU values, but still, changing kern- > abi.h will be problematic from an ABI perspective. Do people care about the > kernel ABI, or is that mainly a userspace issue? Well, we definitely care about the kernel to user ABI. I can't imagine that we're dealing with more than a handful of actual MTU values. Maybe the simplest thing is to extend the mtu enum to include what new values are needed, plus add a function to convert it. (Can we call mulligan?) I don't know how iwarp handles this. Does it just report the wrong mtu, since it doesn't necessarily matter? Steve - any idea here? - Sean -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
