Am 21.08.2015 um 08:12 schrieb Eric Blake:
On 08/20/2015 01:14 AM, Peter Lieven wrote:
If the backend storage is unresponsive and we cancel a request due to
a timeout we cannot immediately destroy the AIOCB because the storage
might complete the original request laster if it is responsive again.
s/laster/later/
For this purpose allow to set the callback to NULL and ignore it in
this case.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
I'll leave the technical review to others, I'm just pointing out grammar.
I am using this one for quite some time now. It seems a good step into solving
the deadlock
problem. The issue is we still need to make the ATAPI calls async. The OS is
only spending 2-3 Minutes
with DMA cancelling and then issues reads again so we still deadlock at the end.
Peter
