From: Eric Blake <eblake@redhat.com>
To: Jeff Cody <jcody@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-block@nongnu.org, armbru@redhat.com,
programmingkidx@gmail.com, jsnow@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH 1/2] util - add automated ID generation utility
Date: Tue, 1 Sep 2015 12:55:15 -0600 [thread overview]
Message-ID: <55E5F493.9060402@redhat.com> (raw)
In-Reply-To: <17356f309b182f0df47567aeed40ab0e3cfc99d3.1441127976.git.jcody@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]
On 09/01/2015 11:23 AM, Jeff Cody wrote:
> Multiple sub-systems in QEMU may find it useful to generated IDs
> for objects that a user may reference via QMP or HMP. This patch
> presents a standardized way to do it, so that automatic ID generation
> follows the same rules.
>
> This patch enforces the following rules when generating an ID:
>
> 1.) Guarantee no collisions with a user-specified ID
> 2.) Identify the sub-system the ID belongs to
> 3.) Guarantee of uniqueness
> 4.) Spoiling predictibility, to avoid creating an assumption
> of object ordering and parsing (i.e., we don't want users to think
> they can guess the next ID based on prior behavior).
>
> The scheme for this is as follows (no spaces):
>
> # subsys D RR
> Reserved char --| | | |
> Subsytem String -----| | |
s/Subsytem/Subsystem/
> Unique number (64-bit) --| |
> Two-digit random number ---|
>
> For example, a generated node-name for the block sub-system may take the
> look like this:
s/take the//
>
> #block076
>
> The caller of id_generate() is responsible for freeing the generated
> node name string with g_free().
>
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> ---
> include/qemu-common.h | 8 ++++++++
> util/id.c | 35 +++++++++++++++++++++++++++++++++++
> 2 files changed, 43 insertions(+)
>
> +char *id_generate(IdSubSystems id)
> +{
> + const char *id_subsys_str[] = {
s/id_/const id_/
> + [ID_QDEV] = "qdev",
> + [ID_BLOCK] = "block",
> + };
Do we want some sort of compile-time assertion that we have entries for
all id values?...
> +
> + static uint64_t id_counters[ID_MAX];
> + uint32_t rnd;
> +
> + assert(id < ID_MAX);
...maybe in the form of assert(id_subsys_str[id])
> +
> + rnd = g_random_int_range(0, 99);
> +
> + return g_strdup_printf("%c%s%" PRIu64 "%" PRId32, ID_SPECIAL_CHAR,
> + id_subsys_str[id],
> + id_counters[id]++,
> + rnd);
> +}
>
Looks reasonable to me.
--
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 --]
next prev parent reply other threads:[~2015-09-01 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 17:23 [Qemu-devel] [RFC PATCH 0/2] Auto-generated IDs Jeff Cody
2015-09-01 17:23 ` [Qemu-devel] [RFC PATCH 1/2] util - add automated ID generation utility Jeff Cody
2015-09-01 18:55 ` Eric Blake [this message]
2015-09-01 19:15 ` Jeff Cody
2015-09-01 19:13 ` John Snow
2015-09-01 19:21 ` Jeff Cody
2015-09-01 17:23 ` [Qemu-devel] [RFC PATCH 2/2] block: auto-generated node-names Jeff Cody
2015-09-01 18:57 ` Eric Blake
2015-09-01 19:25 ` John Snow
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=55E5F493.9060402@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=programmingkidx@gmail.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).