> -----Original Message----- > From: Hefty, Sean [mailto:sean.hefty@xxxxxxxxx] > Sent: Tuesday, June 30, 2015 12:04 PM > To: Jason Gunthorpe; Steve Wise > Cc: 'Sagi Grimberg'; dledford@xxxxxxxxxx; roid@xxxxxxxxxxxx; sagig@xxxxxxxxxxxx; linux-rdma@xxxxxxxxxxxxxxx; infinipath; > eli@xxxxxxxxxxxx; ogerlitz@xxxxxxxxxxxx > Subject: RE: [PATCH V2 4/5] RDMA/iser: support iWARP devices > > > > 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. > > > > There has a been a big push lately to drop the strange transport > > specific stuff - if you are comitted to seeing the access flag clean > > up series through then I don't see a problem with using whatever order > > you like. > > I agree. Ok, then I'll do this: 1) series with iser changes to enable iwarp including mlx/ipath/qib patches to set max_sge_rd 2) series on transport independent access flags / memory reg - updating the kernel ULPs too. Thanks, 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
