On Wed, Nov 18, 2015 at 03:58:48PM +0200, Or Gerlitz wrote: > > Fortunately neither the iSER target or initiator ever support the > > nightmare called bidi commands, > > I honestly don't know why you call it nightmare nor what make you > make that strong assertion. Beause I actually had to deal with block layer code implementing the bidi semantics. > I checked with Alex N. the TGT iser > transport author and he confirmed to me that bidi's worked on TGT, > as for the Linux upstream initiator, I thought that was the case too, but > I never saw it my eyes, and Pete's paper states he had to change the code, > so on that I can't be sure. No need to trust words, we have git. There was absolutely nothing relating to bidi in either the initial iSER checking nor in the changelogs since, and neither has the initial BIDI checking touched iSER. > that's beyond the scope of this thread, I guess.. As is iSER BIDI suppport. Let's thank Sagi for doing a very important performance feature for iSER instead of having this endless discussion about a pointless fringe feature! -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
