From: Kiran Patil <[email protected]>

Reason: Earlier API was designed to be applicable only for storage
initaitor. This new API setps up DDP context for target appropriately
by setting required bits for DDP context. Using earlier 'ddp_setup'
for both (initiator and target) causes problem for DDP offload

Fix: N/A

Notes/Dependencies: This patch depends on the patch which adds "tcm_fc"
module.

Signed-off-by: Kiran Patil <[email protected]>
---

 drivers/target/tcm_fc/tfc_cmd.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/target/tcm_fc/tfc_cmd.c b/drivers/target/tcm_fc/tfc_cmd.c
index 49e5177..d1cb7e5 100644
--- a/drivers/target/tcm_fc/tfc_cmd.c
+++ b/drivers/target/tcm_fc/tfc_cmd.c
@@ -288,8 +288,9 @@ int ft_write_pending(struct se_cmd *se_cmd)
                                cmd->sg_cnt =
                                        T_TASK(se_cmd)->t_tasks_sg_chained_no;
                        }
-                       if (cmd->sg && lport->tt.ddp_setup(lport, ep->xid,
-                                                   cmd->sg, cmd->sg_cnt))
+                       if (cmd->sg && lport->tt.ddp_target(lport, ep->xid,
+                                                           cmd->sg,
+                                                           cmd->sg_cnt))
                                cmd->was_ddp_setup = 1;
                }
        }

_______________________________________________
devel mailing list
[email protected]
https://lists.open-fcoe.org/mailman/listinfo/devel

Reply via email to