On 14/09/14 11:52, Chen Gang wrote: > When failure occurs, need return failure code instead of 0, or the upper > caller will misunderstand. > > Also when retry for EAGAIN reason, better to schedule out for a while, > so can let others have chance to continue their tasks (especially, > their tasks are related EAGAIN under UP kernel).
Is this fixing a real world problem you have seen? xenbus_scanf() and xenbus_printf() already sleep while waiting for the response and delaying isn't going to reduce the likelihood of the transaction being aborted on the retry. David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
