From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Gu Zheng <guz.fnst@cn.fujitsu.com>, Benjamin LaHaise <bcrl@kvack.org>
Cc: linux-aio@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Revert "aio: block exit_aio() until all context requests are completed"
Date: Fri, 15 May 2015 09:41:47 +0200 [thread overview]
Message-ID: <5555A33B.20006@de.ibm.com> (raw)
In-Reply-To: <1431675417-30464-1-git-send-email-borntraeger@de.ibm.com>
I see a significant latency (can be minutes with 2000 disks and HZ=100)
when exiting a QEMU process that has lots of disk devices via aio. The
process sits idle doing nothing as zombie in exit_aio waiting for the
completion.
Turns out that
commit 6098b45b32 ("aio: block exit_aio() until all context requests are
completed") caused the delay.
Patch description was:
It seems that exit_aio() also needs to wait for all iocbs to complete (like
io_destroy), but we missed the wait step in current implemention, so fix
it in the same way as we did in io_destroy.
Now: io_destroy requires to block until everything is cleaned up from its
interface description in the manpage:
DESCRIPTION
The io_destroy() system call will attempt to cancel all outstanding
asynchronous I/O operations against ctx_id, will block on the completion
of all operations that could not be canceled, and will destroy the ctx_id.
Does process exit require the same full blocking? We might be able to
cleanup the process and let the aio data structures be freed lazily.
Opinions or better ideas?
Christian
diff --git a/fs/aio.c b/fs/aio.c
index a793f70..1e6bcdb 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -820,8 +820,6 @@ void exit_aio(struct mm_struct *mm)
for (i = 0; i < table->nr; ++i) {
struct kioctx *ctx = table->table[i];
- struct completion requests_done =
- COMPLETION_INITIALIZER_ONSTACK(requests_done);
if (!ctx)
continue;
@@ -833,10 +831,7 @@ void exit_aio(struct mm_struct *mm)
* that it needs to unmap the area, just set it to 0.
*/
ctx->mmap_size = 0;
- kill_ioctx(mm, ctx, &requests_done);
-
- /* Wait until all IO for the context are done. */
- wait_for_completion(&requests_done);
+ kill_ioctx(mm, ctx, NULL);
}
RCU_INIT_POINTER(mm->ioctx_table, NULL);
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next parent reply other threads:[~2015-05-15 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1431675417-30464-1-git-send-email-borntraeger@de.ibm.com>
2015-05-15 7:41 ` Christian Borntraeger [this message]
2015-05-15 13:42 ` Revert "aio: block exit_aio() until all context requests are completed" Jeff Moyer
2015-05-15 15:26 ` Christian Borntraeger
2015-05-16 15:16 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5555A33B.20006@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=bcrl@kvack.org \
--cc=guz.fnst@cn.fujitsu.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).