On Tue, Nov 17, 2015 at 12:26 PM, Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx> wrote: > >> Why? we don't support and when did we broke it after the initial 2.6.18 >> upstreaming of the driver >> >> Also, do we refuse to queuecommand a bidi? where? > > > Or, bidirectional support is not assumed and needs to be actively set > as a request queue flag (see iscsi_sw_tcp_slave_alloc()). > AFAICT iser never exposed support for bidirectional commands. AFAIR, in the past there weren't explicit means to do that. What's makes iscsi tcp eligible to support bidi's that we don't have @ iser? > Did things change from back in 2.6.18 that we ever carried bidi > commands over iser? AFAIK, Pete Wyckoff had iser working with BIDI commands for few object storage projects. It's been a long time, but I was totally unaware that we don't publish the whatever means needed by upper layers. I copied some 2010 email address of his here... Or. -- 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
