From: Andrew Morton <akpm@linux-foundation.org>
To: Sergey Temerkhanov <temerkhanov@yandex.ru>
Cc: "linux-aio" <linux-aio@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] AIO: always reinitialize iocb->ki_run_list at the end of aio_run_iocb()
Date: Wed, 28 Apr 2010 11:31:49 -0700 [thread overview]
Message-ID: <20100428113149.b912a3e8.akpm@linux-foundation.org> (raw)
In-Reply-To: <201004280251.43430.temerkhanov@yandex.ru>
On Wed, 28 Apr 2010 02:51:43 +0400
Sergey Temerkhanov <temerkhanov@yandex.ru> wrote:
> This patch makes aio_run_iocb() to always reinitialize iocb->ki_run_list (not
> only when iocb->ki_retry() function returns -EIOCBRETRY) so that subsequent
> call of kick_iocb() will succeed.
>
> Regards, Sergey Temerkhanov,
> Cifronic ZAO.
>
>
> [reinit-ki_run_list.patch text/x-patch (657B)]
> diff -r 97344a0f62c9 fs/aio.c
> --- a/fs/aio.c Tue Apr 27 21:18:14 2010 +0400
> +++ b/fs/aio.c Tue Apr 27 21:30:23 2010 +0400
> @@ -748,6 +748,9 @@
> out:
> spin_lock_irq(&ctx->ctx_lock);
>
> + /* will make __queue_kicked_iocb succeed from here on */
> + INIT_LIST_HEAD(&iocb->ki_run_list);
> +
> if (-EIOCBRETRY == ret) {
> /*
> * OK, now that we are done with this iteration
> @@ -756,8 +759,6 @@
> * "kick" can start the next iteration
> */
>
> - /* will make __queue_kicked_iocb succeed from here on */
> - INIT_LIST_HEAD(&iocb->ki_run_list);
> /* we must queue the next iteration ourselves, if it
> * has already been kicked */
> if (kiocbIsKicked(iocb)) {
I assume that this fixes some runtime problem which you observed?
Can you please describe that problem? This code is pretty old - what
was your application doing that nobody else's application has thus far
done?
Also, please send your Signed-off-by: for this patch, as per
Documentation/Submittingpatches, thanks.
next prev parent reply other threads:[~2010-04-28 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 22:51 Sergey Temerkhanov
2010-04-28 18:31 ` Andrew Morton [this message]
2010-04-29 22:56 ` Sergey Temerkhanov
2010-05-21 21:47 ` Andrew Morton
2010-05-26 19:38 ` Jeff Moyer
2010-05-27 10:06 ` Sergey Temerkhanov
2010-06-01 21:14 ` Jeff Moyer
2010-06-24 17:31 ` Sergey Temerkhanov
2010-06-27 16:10 ` Jeff Moyer
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=20100428113149.b912a3e8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=temerkhanov@yandex.ru \
/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
Powered by JetHome