On 03/22/2012 09:52 AM, Christoph Hellwig wrote: > On Wed, Mar 21, 2012 at 05:47:33PM -0700, Nicholas A. Bellinger wrote: >> So for single task operation, the transport_do_task_sg_chain() logic is >> not required because sg_chain() is never called with only a single >> se_task->task_sg[] present per se_cmd. >> >> For > 1 task operation in transport_allocate_data_tasks(), the >> transport_do_task_sg_chain() is still required (along with an extra SGL >> per se_task->task_sg[] for the link) in order for a se_cmd's SGLs to be >> made into a single walkable list using scatterlist.h primitives. >> >> So no, I don't think we can get rid of transport_do_task_sg_chain() >> logic as it's still a hard requirement for > 1 task operation. > > Unless we kill task completely, which we really should. Please tell us more. Wasn't the point of task that backstores didn't need to be written to handle arbitrarily large xfers? Regards -- Andy -- 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
