> > > TBH, I think this would be much better off integrating with the > > > existing paths tcpdump/setc uses rather than yet again something new > > > > This ties in with the existing MAD interface, which isn't going away > > anytime soon, if ever. > > I didn't say the MAD interface was going away, I said it was not the > interface everything else in the kernel uses for packet capture.
My focus is tying this functionality in with the existing IB stack. The MAD, verbs, and HCA drivers do not use net_device, sk_buff, or anything in netdev, and I don't have the time or inclination to try to add it. We have an interface that allows registration to receive MADs; this provides a simple extension of that interface. I'm mainly interested in capturing MAD data, not all packets. We don't have access to any of the headers, or even an easy way to know the destination for sent MADs. - 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
