From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH] block: Use a GString in bdrv_perm_names()
Date: Tue, 14 Jan 2020 13:50:41 +0100 [thread overview]
Message-ID: <c2436d27-e130-4e38-e981-78c4f929ca5b@redhat.com> (raw)
In-Reply-To: <20200110171518.22168-1-berto@igalia.com>
On 1/10/20 6:15 PM, Alberto Garcia wrote:
> This is a bit more efficient than having to allocate and free memory
> for each new permission.
>
> The default size (30) is enough for "consistent read, write, resize".
>
> Signed-off-by: Alberto Garcia <berto@igalia.com>
> ---
> block.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/block.c b/block.c
> index 1b6f7c86e8..2bc9e58392 100644
> --- a/block.c
> +++ b/block.c
> @@ -1976,18 +1976,19 @@ char *bdrv_perm_names(uint64_t perm)
> { 0, NULL }
> };
>
> - char *result = g_strdup("");
> + GString *result = g_string_sized_new(30);
> struct perm_name *p;
>
> for (p = permissions; p->name; p++) {
> if (perm & p->perm) {
> - char *old = result;
> - result = g_strdup_printf("%s%s%s", old, *old ? ", " : "", p->name);
> - g_free(old);
> + if (result->len > 0) {
> + g_string_append(result, ", ");
> + }
> + g_string_append(result, p->name);
> }
> }
>
> - return result;
> + return g_string_free(result, FALSE);
> }
Maybe similar cleanup can be done to report_unsupported_feature() in
block/qcow2.c.
prev parent reply other threads:[~2020-01-14 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 17:15 [PATCH] block: Use a GString in bdrv_perm_names() Alberto Garcia
2020-01-10 19:25 ` Eric Blake
2020-01-14 12:11 ` Max Reitz
2020-01-14 12:50 ` Philippe Mathieu-Daudé [this message]
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=c2436d27-e130-4e38-e981-78c4f929ca5b@redhat.com \
--to=philmd@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).