> -----Original Message----- > From: linux-rdma-owner@xxxxxxxxxxxxxxx [mailto:linux-rdma-owner@xxxxxxxxxxxxxxx] On Behalf Of Hefty, Sean > Sent: Thursday, June 25, 2015 2:20 PM > To: Jason Gunthorpe > Cc: Steve Wise; linux-rdma@xxxxxxxxxxxxxxx; sagig@xxxxxxxxxxxx; orgerlitz@xxxxxxxxxxxx; Roi Dayan > Subject: RE: [PATCH RFC 2/2] RDMA/isert: Support iWARP transport > > > What about moving to something more specific? Encode the allowed verbs > > in the access flag? > > This makes more sense to me. Something like: SEND, RECV, INIT READ, INIT WRITE, READ TARGET, WRITE TARGET, etc. We're close to > this, but it's not clear, for example, what flags are needed for a receive buffer. None? LOCAL_WRITE? Make sense to me too. To stage the changes we could introduce a new function that returns the needed ib_access_flags value given the desired opcodes. Then have a series that changes all the existing ULPs to make use of this new function. Steve. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
