qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/1] qtest: pre-buffer hex nibs
Date: Thu, 07 May 2015 14:21:02 -0600	[thread overview]
Message-ID: <554BC92E.1090401@redhat.com> (raw)
In-Reply-To: <1431021095-7558-2-git-send-email-jsnow@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]

On 05/07/2015 11:51 AM, John Snow wrote:
> Instead of converting each byte one-at-a-time and then sending each byte
> over the wire, use sprintf() to pre-compute all of the hex nibs into a
> single buffer, then send the entire buffer all at once.
> 
> This gives a moderate speed boost to memread() and memwrite() functions.
> 
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---

> -        qtest_send_prefix(chr);
> -        qtest_send(chr, "OK 0x");
> +        enc = g_malloc(2 * len + 1);
>          for (i = 0; i < len; i++) {
> -            qtest_sendf(chr, "%02x", data[i]);
> +            sprintf(&enc[i * 2], "%02x", data[i]);

Making a function call to sprintf() has a lot of overhead.  Isn't it
even faster to open-code the conversion, something like:

for (i = 0; i < len; i++) {
    const char digits[] = "0123456789abcdef";
    enc[i * 2] = digits[data[i] >> 4];
    enc[i * 2 + 1] = digits[data[i] & 0xf];
}
enc[len * 2] = '\0';

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2015-05-07 20:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 17:51 [Qemu-devel] [PATCH 0/1] qtest: hex nib buffering John Snow
2015-05-07 17:51 ` [Qemu-devel] [PATCH 1/1] qtest: pre-buffer hex nibs John Snow
2015-05-07 20:21   ` Eric Blake [this message]
2015-05-07 20:26     ` John Snow
2015-05-08 17:15   ` Markus Armbruster

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=554BC92E.1090401@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).