On Jul 17, 2013, at 12:06 AM, "Hefty, Sean" <[email protected]> wrote:
> I don't remember. Is it known how the mtu is communicated with the kernel?
I hadn't looked at the kernel side yet; I was waiting for the userspace side to
sort itself out first.
> Looking at kern-abi.h, the mtu fields are:
>
> struct ibv_query_port_resp {
> __u8 max_mtu;
> __u8 active_mtu;
>
> struct ibv_kern_qp_attr {
> __u32 path_mtu;
>
> struct ibv_query_qp_resp {
> __u8 path_mtu;
>
> struct ibv_modify_qp {
> __u8 path_mtu;
>
> In most cases, we only have 8 bits available to/from the kernel. (There are
> at least 16 bits of reserved space in these structures.)
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?
--
Jeff Squyres
[email protected]
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
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
