public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@kvack.org>
To: Suparna Bhattacharya <suparna@in.ibm.com>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] aio_down() for i386 and x86_64
Date: Wed, 15 Jun 2005 15:18:30 -0400	[thread overview]
Message-ID: <20050615191830.GA28261@kvack.org> (raw)
In-Reply-To: <20050615165349.GA4521@in.ibm.com>

On Wed, Jun 15, 2005 at 10:23:49PM +0530, Suparna Bhattacharya wrote:
> Interesting approach - using ki_wait.private for this.
> Could we make aio_down take a wait queue parameter as well instead of
> the iocb ?

Hmmm, I guess there might be instances where someone has to wait on 
multiple wait queues.  Will add that to the next version of the patch.

> Need to think a little about impact on io cancellation.

It should be possible to cancel semaphore operations fairly easily -- 
the aio_down function can set ->ki_cancel to point to a semaphore cancel 
routine.  I'll give coding that a try.

> BTW, is the duplication of functions across architectures still needed ? I
> thought that one of advantages of implementing a separate aio_down
> routine vs modifiying down to become retryable was to get away from
> that ... or wasn't it ?

Good point.  The fast path for down() will probably need to remain a 
separate function, but we could well unify the code with the 
down_interruptible() codepath.

> Meanwhile, I probably need to repost my aio_wait_bit patches - there
> may be some impact here.

Sure -- any version of those would be useful to build on.  Cheers!

		-ben

  reply	other threads:[~2005-06-15 19:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 21:50 [RFC] aio_down() for i386 and x86_64 Benjamin LaHaise
2005-06-15 16:53 ` Suparna Bhattacharya
2005-06-15 19:18   ` Benjamin LaHaise [this message]
2005-06-16 13:02     ` Suparna Bhattacharya

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=20050615191830.GA28261@kvack.org \
    --to=bcrl@kvack.org \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suparna@in.ibm.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