All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ankit Jain <jankit@suse.de>
To: Kent Overstreet <koverstreet@google.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	Jan Kara <jack@suse.cz>, Zach Brown <zab@zabbo.net>,
	tytso@mit.edu
Subject: Re: [LSF/MM TOPIC][ATTEND] Improving async io, specifically io_submit latencies
Date: Tue, 05 Mar 2013 01:25:16 +0530	[thread overview]
Message-ID: <5134FC24.3080009@suse.de> (raw)
In-Reply-To: <20130228210318.GA3762@google.com>

On 03/01/2013 02:33 AM, Kent Overstreet wrote:
> On Fri, Mar 01, 2013 at 01:37:55AM +0530, Ankit Jain wrote:
>> 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?
> 
> Was just talking about this.  Completely agreed that we need to do
> something about it, but personally I don't think punting everything to
> workqueue is a realistic solution.

Sure. Like you and others mentioned on this thread, there are possible
ways to solve this. I think it would be useful to discuss those and
figure out an approach to try for this, at the conference.

Thanks,
-- 
Ankit Jain
SUSE Labs

      parent reply	other threads:[~2013-03-04 19:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 20:07 [LSF/MM TOPIC][ATTEND] Improving async io, specifically io_submit latencies Ankit Jain
2013-02-28 21:03 ` 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 [this message]

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=5134FC24.3080009@suse.de \
    --to=jankit@suse.de \
    --cc=jack@suse.cz \
    --cc=koverstreet@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=tytso@mit.edu \
    --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 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.