Am 16.04.2015 um 15:17 schrieb Paolo Bonzini: > > On 16/04/2015 15:02, Peter Lieven wrote: >>> Also, I think it is iscsi_co_generic_cb that should set >>> force_next_flush, so that it is only set on failure. Not really for the >>> optimization value, but because it's clearer. >> I don't get what you mean with it should only "set on failure". >> My approach would be to add a flag to the iTask that the command >> requires to set force_flush after successful completion. Is it that >> what you mean? > Set on success. Lack of sleep.
I have send a v2 following your suggestions. Peter
