mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Sergey Temerkhanov <temerkhanov@cifronik.ru>
Cc: Sergey Temerkhanov <temerkhanov@yandex.ru>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-aio" <linux-aio@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Benjamin LaHaise <bcrl@kvack.org>,
	Zach Brown <zach.brown@oracle.com>,
	Suparna Bhattacharya <suparna@in.ibm.com>
Subject: Re: [PATCH][RFC] AIO: always reinitialize iocb->ki_run_list at the end of aio_run_iocb()
Date: Sun, 27 Jun 2010 12:10:32 -0400	[thread overview]
Message-ID: <x49sk48318n.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <201006242131.21463.temerkhanov@cifronik.ru> (Sergey Temerkhanov's message of "Thu, 24 Jun 2010 21:31:21 +0400")

Sergey Temerkhanov <temerkhanov@cifronik.ru> writes:

> The problem with kick_iocb() is exactly as this: If retry() method 
> returns -EIOCBQUEUED to aio_run_iocb() then any subsequent call to 
> kick_iocb() results in failure. Is it expected behavior?

 * If ki_retry returns -EIOCBQUEUED it has made a promise that aio_complete()
 * will be called on the kiocb pointer in the future.  The AIO core will
 * not ask the method again -- ki_retry must ensure forward progress.

Does that answer your question?

Cheers,
Jeff

      reply	other threads:[~2010-06-27 16:10 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
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 [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=x49sk48318n.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bcrl@kvack.org \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suparna@in.ibm.com \
    --cc=temerkhanov@cifronik.ru \
    --cc=temerkhanov@yandex.ru \
    --cc=zach.brown@oracle.com \
    /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
all inboxes | Powered by JetHome®