From: Jens Axboe <axboe@kernel.dk>
To: Tejun Heo <tj@kernel.org>,
kent.overstreet@gmail.com, Benjamin LaHaise <bcrl@kvack.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: serial percpu_ref draining in exit_aio()
Date: Thu, 19 Mar 2015 14:25:57 -0600 [thread overview]
Message-ID: <550B30D5.9080207@kernel.dk> (raw)
In-Reply-To: <20150319173413.GU25365@htj.duckdns.org>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
On 03/19/2015 11:34 AM, Tejun Heo wrote:
> Hello,
>
> So, Jens noticed that fio process exiting takes seconds when there are
> multiple aio contexts and the culprit seems to be the serial
> percpu_ref draining in exit_aio(). It's generally a bad idea to
> expose RCU latencies to userland because they add up really quickly
> and are unrelated to other performance parameters. Can you guys
> please at least update the code so that it waits for all percpu_refs
> to drain at the same time rather than one after another? That should
> resolve the worst part of the problem.
This works for me. Before:
real 0m5.872s
user 0m0.020s
sys 0m0.040s
after
real 0m0.246s
user 0m0.020s
sys 0m0.040s
It solves the exit_aio() issue, but if the app calls io_destroy(), then
we are back to square one...
--
Jens Axboe
[-- Attachment #2: aio-exit-parallel.patch --]
[-- Type: text/x-patch, Size: 1686 bytes --]
diff --git a/fs/aio.c b/fs/aio.c
index f8e52a1854c1..73b0de46577b 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -805,18 +805,35 @@ EXPORT_SYMBOL(wait_on_sync_kiocb);
void exit_aio(struct mm_struct *mm)
{
struct kioctx_table *table = rcu_dereference_raw(mm->ioctx_table);
+ struct completion *comp = NULL;
int i;
if (!table)
return;
+ if (table->nr > 1) {
+ comp = kmalloc(table->nr * sizeof(struct completion),
+ GFP_KERNEL);
+ if (comp)
+ for (i = 0; i < table->nr; i++)
+ init_completion(&comp[i]);
+ }
+
for (i = 0; i < table->nr; ++i) {
struct kioctx *ctx = table->table[i];
struct completion requests_done =
COMPLETION_INITIALIZER_ONSTACK(requests_done);
- if (!ctx)
+ /*
+ * Complete it early, so the below wait_for_completion()
+ * doesn't expect a complete() from the RCU callback
+ */
+ if (!ctx) {
+ if (comp)
+ complete(&comp[i]);
continue;
+ }
+
/*
* We don't need to bother with munmap() here - exit_mmap(mm)
* is coming and it'll unmap everything. And we simply can't,
@@ -825,10 +842,20 @@ 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);
+ if (comp)
+ kill_ioctx(mm, ctx, &comp[i]);
+ else {
+ kill_ioctx(mm, ctx, &requests_done);
+ wait_for_completion(&requests_done);
+ }
+ }
- /* Wait until all IO for the context are done. */
- wait_for_completion(&requests_done);
+ if (comp) {
+ for (i = 0; i < table->nr; i++) {
+ /* Wait until all IO for the context are done. */
+ wait_for_completion(&comp[i]);
+ }
+ kfree(comp);
}
RCU_INIT_POINTER(mm->ioctx_table, NULL);
next prev parent reply other threads:[~2015-03-19 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 17:34 serial percpu_ref draining in exit_aio() Tejun Heo
2015-03-19 20:25 ` Jens Axboe [this message]
2015-03-19 20:58 ` Jeff Moyer
2015-03-19 21:00 ` Tejun Heo
2015-03-19 21:27 ` Jens Axboe
2015-03-19 21:43 ` Jens Axboe
2015-03-20 18:56 ` Jeff Moyer
2015-03-20 19:21 ` 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=550B30D5.9080207@kernel.dk \
--to=axboe@kernel.dk \
--cc=bcrl@kvack.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.