From: Rutger ter Borg <rutger@terborg.net>
To: ceph-devel@vger.kernel.org
Subject: Rados and user-provided buffers
Date: Wed, 18 Sep 2013 21:57:55 +0200 [thread overview]
Message-ID: <l1d0jr$jqa$1@ger.gmane.org> (raw)
Dear all,
I've a question regarding buffers in rados (using the C++ API). I'm
allocating and using my own buffers, and would like to read and write
directly into and from them. I'm using a bufferlist consisting of
static_buffers, which are passed to Rados' aio_read and aio_write.
For aio_write, rados works as expected, i.e., the bufferlist is returned
as it was before the call. However, when doing aio_read, it seems that
the bufferlist is destroyed (not used) in the call, despite all the
buffers being static.
Is this expected behaviour? I read a thread "read/write on RADOS using
external buffer" from this mailing list from 2010, but wasn't able to
figure out whether rados does or doesn't support reading into
user-provided static_buffers.
Thanks in advance,
Cheers,
Rutger
next reply other threads:[~2013-09-18 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 19:57 Rutger ter Borg [this message]
2013-09-18 20:01 ` Rados and user-provided buffers Sage Weil
2013-09-18 20:31 ` Rutger ter Borg
2013-09-18 20:52 ` Sage Weil
2013-09-19 9:28 ` Rutger ter Borg
2013-09-19 12:39 ` 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='l1d0jr$jqa$1@ger.gmane.org' \
--to=rutger@terborg.net \
--cc=ceph-devel@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.