All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Rutger ter Borg <rutger@terborg.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Multiple concurrent async ops per IoCtx?
Date: Wed, 29 Aug 2012 07:41:28 -0700	[thread overview]
Message-ID: <503E2A18.5000603@inktank.com> (raw)
In-Reply-To: <k1ksi5$q2p$1@ger.gmane.org>

On 08/29/2012 03:57 AM, Rutger ter Borg wrote:
>
> Dear list,
>
> are Rados' IoCtx objects able to process multiple asynchronous
> operations at the same time, or is it necessary to wait for an operation
> to complete, before issuing a following operation?
>
> I.e., can I do the following and expect it to work?
>
> IoCtx ctx;
> ctx.aio_read( ... read 1 ... );
> ctx.aio_read( ... read 2 ... );
> ctx.aio_read( ... read 3 ... );
>
> ... time passes ...
>
> read 3 completes (e.g.)
> read 1 completes
> read 2 completes
>
> TIA,
> Cheers,
>
> Rutger

Yes, all the asynchronous functions can run in parallel. An IoCtx
has little bearing on performance - it mostly just saves you from
specifying the full set of parameters (i.e. pool, snapshot id, snapshot
context, etc.) for each operation.

Are you seeing behavior that looks like the aio operations aren't being 
run in parallel?

Josh

  parent reply	other threads:[~2012-08-29 14:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 10:57 Multiple concurrent async ops per IoCtx? Rutger ter Borg
2012-08-29 13:40 ` qemu-rbd : savevm monitor command don't save vmstate, is it normal ? Alexandre DERUMIER
2012-08-29 13:48   ` Smart Weblications GmbH - Florian Wiessner
2012-08-29 14:25     ` Alexandre DERUMIER
2012-08-29 16:15   ` Josh Durgin
2012-08-29 16:25     ` Yehuda Sadeh
2012-08-29 17:05       ` Josh Durgin
2012-08-29 16:29     ` Alexandre DERUMIER
2012-08-29 14:41 ` Josh Durgin [this message]
2012-08-30 12:16   ` Multiple concurrent async ops per IoCtx? Rutger ter Borg

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=503E2A18.5000603@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=rutger@terborg.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.