Jason Gunthorpe <jguntho...@obsidianresearch.com> wrote: > I think you should have split this patch up, there is lots going on here. > - Add proper TSS that doesn't change the wire protocol > - Add fake TSS that does change the wire protocol, and > properly document those changes so other people can follow/implement them > - Add RSS [...] > Specifically it means the requirements for alignment and > contiguous-ness are gone. This means you can implement it without > using the QP groups API and it will work immediately with every HCA > out there. I think if we are going to actually mess with the wire > protocol this sort of broad applicability is important.
We can break the TSS patches to be two staged, sure. As for "you can implement it without using the QP groups API" do we agree that for the RSS use case the QP groups API for kernel verbs consumers (== IPoIB) does make sense? > As for the other two questions: seems reasonable to me. Without a > consensus among HW vendors how to do this it makes sense to move ahead > *in the kernel* with a minimal API. Userspace is a different question of > course.. Sean, are you OK with that approach, of sticking to the current concepts but expose them only at kernel space for the time being? Or. -- 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
