On Thu, 2014-01-16 at 12:13 -0800, Roland Dreier wrote: > > > On Mon, 2014-01-13 at 12:32 -0800, Nicholas A. Bellinger wrote: > > > Hi Roland & Co, > > > > > > Just curious if your planning to take a look at this series soon for > > > v3.14 code..? > > > > > > As you might imagine, I'd like to see it merged this round in order to > > > move forward on iser-target protection for v3.15. > > > > > > Are there any specific issues that you'd like to see addressed for an > > > initial merge..? > > I haven't really had a chance to look at the new API and decide if it > makes sense as the way to expose these features. Have you looked at > the new kernel API? Any thoughts? I've reviewed the API from the perspective of what's required for implementing protection support in iser, and currently don't have any recommendations or objections beyond what has been proposed by Sagi & Co in PATCH-v4 code. > How does it compare with how other subsystems have exposed protection > info? > So there is not a interface in SCSI land for interacting (directly) with hardware protection support, as it's primarily just telling SCSI what protection modes are supported while the rest is implemented in vendor specific firmware interfaces. (CC'ing MKP) > Right now I'm dealing with fixing the fallout from picking up the "IP > addressing for IBoE" and other patch sets that were supposedly "ready > to merge for a long time" so I'm not sure I'll get to the protection > changes in time for 3.14. > Pretty please for v3.14..? Sagi & Co are committed to supporting the changes, and are ready to do what's necessary for a merge. AFAICT the series has gone through enough list review over the last months without (serious) objections, so I'm not sure what else is necessary to move forward for a merge, aside from your input of course. :-) --nab -- 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
