> > The TCP/IP filters are broken into separate filters based in L4/L3. It > > would > seem to > > make sense if the IB filters were similarly divided into L2/L3/L4 filters. > IB and IPv6 > > could probably share the same filter definition. > > IPv6 filters wasn't defined through this submission, but as I wrote, > the scheme provided allows for adding more filters and flow specs.
My point was that the IPv6 filter should be defined and used here. The following basic filters were defined: ethernet - src/dst mac ... ip - src/dst ip tcp/udp - src/dst port These are at least somewhat intuitive to me. The IB filter is ib - (src/dst?) qpn, dgid This is equivalent to creating a filter that's: tcpip - port, dst ip IMO, it would be better to define IB filters using the same structure that you used for tcp/ip/ethernet. For example ibqp - src/dst qpn (pkey?) ipv6 - src/dst ipv6/gids (flowlabel?) iblink - src/dst lids, (sl?) If the hardware can only support matching on the qpn and dgid, then it can simply fail any requests which specify a non-zero mask on the unsupported components. - 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
