From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: aio_down() patch series -- cancellation support added
Date: Thu, 23 Jun 2005 18:59:26 +0530 [thread overview]
Message-ID: <20050623132926.GA6669@in.ibm.com> (raw)
In-Reply-To: <20050620214614.GC6628@kvack.org>
On Mon, Jun 20, 2005 at 05:46:14PM -0400, Benjamin LaHaise wrote:
> Add linux-kernel to the Cc list...
>
> On Mon, Jun 20, 2005 at 05:38:35PM -0400, Benjamin LaHaise wrote:
> > Hello all,
> >
> > The patch series at http://www.kvack.org/~bcrl/patches/aio-2.6.12-A1/
> > now adds support for cancellation of an aio_down() operation. The
> > races should be correctly handled by introducing per-kiocb locking
> > that serialises ->ki_cancel() and ->ki_retry(). The interesting patch
> > additions are 40_lock_kiocb 50_aio_down_cancel.diff. Comments?
> >
> > -ben
> > --
One quick question.
Since lock_kiocb() may block, does that mean that the aio worker thread
could be put to sleep while an iocb cancellation is in progress, even though
there may be other iocbs/ioctx's to process ?
Looking at the rest a little more closely in terms of how everything
will fit together, a few questions come to mind - need to think
about it a little more. I guess the main reason you need the aio_down_wait
callback is to make sure the semaphore is grabbed right in the context
of the wakeup rather than at retry time, is that correct ?
Regards
Suparna
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India
next prev parent reply other threads:[~2005-06-23 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050620213835.GA6628@kvack.org>
2005-06-20 21:46 ` aio_down() patch series -- cancellation support added Benjamin LaHaise
2005-06-23 13:29 ` Suparna Bhattacharya [this message]
2005-06-23 16:41 ` Benjamin LaHaise
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=20050623132926.GA6669@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=bcrl@kvack.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.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.