> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Hefty, Sean > Sent: Thursday, June 25, 2015 1:30 PM > To: Jason Gunthorpe; Steve Wise > Cc: [email protected]; [email protected]; [email protected]; > [email protected] > Subject: RE: [PATCH RFC 2/2] RDMA/isert: Support iWARP transport > > > > + * IWARP transports need REMOTE_WRITE for MRs used as the target of > > > + * an RDMA_READ. Since the DMA MR is used for all ports, then if > > > + * any port is running IWARP, add REMOTE_WRITE. > > > + */ > > > + if (any_port_is_iwarp(device)) > > > > It would be nice to have a new-style cap test for this instead of open > > coding iwarp. Similar to rdma_cap_read_multi_sge > > This should be pushed down into the devices, or at least within verbs, rather > than having ULPs needing to know this oddness.
How would you envision doing this? At the time a MR is registered the device driver doesn't know if the application will be doing RDMA reads or not on that MR. Steve. -- 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
