libaio: don't call io_destroy(), let exit_aio() take care of it

[fio.git] / engines / libaio.c

diff --git a/engines/libaio.c b/engines/libaio.c
index 12f3b366d71be5c521a67d238878f0f3a947ad2d..8ba21f8959b318939786aaa21b96e21f7485d8c5 100644 (file)
--- a/engines/libaio.c
+++ b/engines/libaio.c
@@ -37,7 +37,7 @@ struct libaio_data {
 };
 
 struct libaio_options {
-       struct thread_data *td;
+       void *pad;
        unsigned int userspace_reap;
 };
 
@@ -281,7 +281,7 @@ static int fio_libaio_commit(struct thread_data *td)
                        }
                        if (!wait_start) {
                                fio_gettime(&tv, NULL);
-                               wait_start = 0;
+                               wait_start = 1;
                        } else if (mtime_since_now(&tv) > 30000) {
                                log_err("fio: aio appears to be stalled, giving up\n");
                                break;
@@ -316,7 +316,14 @@ static void fio_libaio_cleanup(struct thread_data *td)
        struct libaio_data *ld = td->io_ops->data;
 
        if (ld) {
-               io_destroy(ld->aio_ctx);
+               /*
+                * Work-around to avoid huge RCU stalls at exit time. If we
+                * don't do this here, then it'll be torn down by exit_aio().
+                * But for that case we can parallellize the freeing, thus
+                * speeding it up a lot.
+                */
+               if (!(td->flags & TD_F_CHILD))
+                       io_destroy(ld->aio_ctx);
                free(ld->aio_events);
                free(ld->iocbs);
                free(ld->io_us);