Re: [PATCH 0/2] Include protection information in iscsi header

2014-06-05 Thread Sagi Grimberg
On 6/3/2014 9:16 AM, Roland Dreier wrote: On Sun, Jun 1, 2014 at 9:19 AM, Sagi Grimberg sa...@mellanox.com wrote: Although these patches involve 3 subsystems with different maintainers (scsi, iser, target) I would prefer seeing these patches included together. Why? Because they break wire

Re: [PATCH 0/2] Include protection information in iscsi header

2014-06-03 Thread Roland Dreier
On Sun, Jun 1, 2014 at 9:19 AM, Sagi Grimberg sa...@mellanox.com wrote: Although these patches involve 3 subsystems with different maintainers (scsi, iser, target) I would prefer seeing these patches included together. Why? Because they break wire compatibility? I hate to say it but even if

Re: [PATCH 0/2] Include protection information in iscsi header

2014-06-03 Thread Or Gerlitz
On Tue, Jun 3, 2014 at 9:16 AM, Roland Dreier rol...@purestorage.com wrote: On Sun, Jun 1, 2014 at 9:19 AM, Sagi Grimberg sa...@mellanox.com wrote: Although these patches involve 3 subsystems with different maintainers (scsi, iser, target) I would prefer seeing these patches included together.

[PATCH 0/2] Include protection information in iscsi header

2014-06-01 Thread Sagi Grimberg
At the SCSI transport level, there is no distinction between user data and protection information. Thus, iscsi header field expected data transfer length should include protection information. This set modifies both the iscsi initiator (patch #1), and target (patch #2) to expect data length which