Williams, Dan J wrote: > Some engines optimize operation by reading ahead in the descriptor chain > such that descriptor2 may start execution before descriptor1 completes. > If descriptor2 depends on the result from descriptor1 then a fence is > required (on descriptor2) to disable this optimization. The async_tx > api could implicitly identify dependencies via the 'depend_tx' > parameter, but that would constrain cases where the dependency chain > only specifies a completion order rather than a data dependency. So, > provide an ASYNC_TX_FENCE to explicitly identify data dependencies. > > Signed-off-by: Dan Williams <dan.j.williams@xxxxxxxxx> > --- Signed-off-by: Maciej Sosnowski <maciej.sosnowski@xxxxxxxxx>-- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
