From: Casey Bodley <cbodley@redhat.com>
To: David Disseldorp <ddiss@suse.de>, ceph-devel@vger.kernel.org
Subject: Re: memcpy() avoidance using decode(bufferlist)
Date: Fri, 22 Apr 2016 14:05:15 -0400 [thread overview]
Message-ID: <571A67DB.6010903@redhat.com> (raw)
In-Reply-To: <20160422155355.06c5ef4c@echidna.suse.de>
On 04/22/2016 09:53 AM, David Disseldorp wrote:
> Hi,
>
> A question regarding bufferlist usage:
>
> I'm working on the cmpext librados C API, and want to decode the OSD
> response directly into a (char *buf/size_t len) buffer provided by the
> caller.
>
> I figured this would be straightforward via:
> bl.push_back(buffer::create_static(buf, len));
> ...
> ::decode_nohead(iter.get_remaining(), bl, iter);
>
> However, the decoded data doesn't make it into buf, unless an extra copy
> occurs via:
> bl.copy(0, bl.length(), buf);
>
> Any suggestions on a clean way to avoid the extra copy here?
>
> Cheers, David
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi David,
The decode logic is appending data to the end of the given bufferlist,
which is why it's skipping over the buffer pointer that you provide.
Internally, buffer::list is allocating its own 'buffer::ptr
append_buffer' to batch these appends. This append_buffer is not
currently exposed by the interface, but if there was a way to provide
your own buffer::ptr from buffer::create_static(), you could
hypothetically use that to avoid the copy.
Casey
next prev parent reply other threads:[~2016-04-22 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 13:53 memcpy() avoidance using decode(bufferlist) David Disseldorp
2016-04-22 18:05 ` Casey Bodley [this message]
2016-04-24 22:56 ` David Disseldorp
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=571A67DB.6010903@redhat.com \
--to=cbodley@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ddiss@suse.de \
/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.