> -----Original Message----- > From: Sagi Grimberg [mailto:[email protected]] > Sent: Tuesday, June 30, 2015 4:26 AM > To: Steve Wise; [email protected] > Cc: [email protected]; [email protected]; [email protected]; > [email protected]; [email protected]; > [email protected]; [email protected]; [email protected] > Subject: Re: [PATCH V2 4/5] RDMA/iser: support iWARP devices > > On 6/30/2015 12:36 AM, Steve Wise wrote: > > Limit the sg tablesize based on the device fast reg depth. > > > > Use rdma_get_dma_mr() to allocate the DMA MR. > > > > Use rdma_fast_reg_access_flags() to set the access_flags for fast > > register work requests. > > Steve, > > I wander if it would make more sense to get the iser/isert stuff in > without the mr stuff (I'd like the mr to go in a different direction). > > Whatever you prefer. >
I prefer to decouple the iSER changes with this core work. Jason/Sean... thoughts? I could do the iSER w/o patch 3, and the follow up with a series that includes our final solution on transport independent memory registration and change all the TI kernel users (iser and nfsrdma) along with it. 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
