On Tue, Nov 07, 2017 at 10:32:15AM -0700, Jason Gunthorpe wrote: > On Tue, Nov 07, 2017 at 11:15:12AM -0600, Daniel Jurgens wrote: > > > This flow is through ib_modify_qp, it's not user space specific. If > > it really pains you that much it can be changed an inclusive compare > > instead of exclusive. > > There was already a RFC on re-purpsing those constants and exposing > them to user space. It pains me, the flows of create_qp/modify_qp are completely unmaintainable mess and I would like to see more explicit checks, so refactoring will be easy. We will reach that step much sooner than I expected. Thanks BTW, I spent last day to annotate all different paths of create_qp for the resource tracking information. > > Jason
Attachment:
signature.asc
Description: PGP signature
