From: Ankit Jain <jankit@suse.de>
To: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org
Cc: Jan Kara <jack@suse.cz>, Zach Brown <zab@zabbo.net>
Subject: [LSF/MM TOPIC][ATTEND] Improving async io, specifically io_submit latencies
Date: Fri, 01 Mar 2013 01:37:55 +0530 [thread overview]
Message-ID: <512FB91B.80102@suse.de> (raw)
Hi,
I'm interested in discussing how to improve async io api in the kernel,
specifically io_submit latencies.
I am working on trying to make io_submit non-blocking. I had posted a
patch[1] for this earlier on fsdevel and there was some discussion on
it. I have made some of the improvements suggested there.
The approach attempted in that patch essentially tries to service the
requests on a separate kernel thread. It was pointed out that this would
need to ensure that there aren't any unknown task_struct references or
dependencies under f_op->aio* which might get confused because of the
kernel thread. Would this kinda full audit be enough or would be it
considered too fragile?
I would like to discuss whether this is best approach for solving this
problem, and/or discuss some of the other possible approaches to solving
this issue.
This has been discussed in the past but we don't seem to have a solution
as of now.
References:
1. http://comments.gmane.org/gmane.linux.kernel.aio.general/3142
Regards,
--
Ankit Jain
SUSE Labs
next reply other threads:[~2013-02-28 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 20:07 Ankit Jain [this message]
2013-02-28 21:03 ` [LSF/MM TOPIC][ATTEND] Improving async io, specifically io_submit latencies Kent Overstreet
2013-02-28 23:49 ` Zach Brown
2013-03-01 15:03 ` Jeff Moyer
2013-03-01 16:20 ` Tejun Heo
2013-03-01 16:31 ` Tejun Heo
2013-03-04 19:55 ` Ankit Jain
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=512FB91B.80102@suse.de \
--to=jankit@suse.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=zab@zabbo.net \
/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).