Hi Nic, I'm trying to understand how transport_do_task_sg_chain() is used in the current stack. I'm not sure if I'm missing something, or if all this logic can be eliminated. It looks like we always have an sg list in the se_cmd, and then when we split the command into tasks, we put a sublist of that sg list into each task. Then all transport_do_task_sg_chain() does is chain those sublists back together into a new chained list that AFAICT is equivalent to the command's original sg list. So does it make sense to get rid of this task_sg_chaining logic and just have the fabrics use commands' sg lists directly, or is there something deeper here that I'm not seeing? Thanks, - R. -- 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
