From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-block@nongnu.org, jsnow@redhat.com,
armbru@redhat.com, programmingkidx@gmail.com, berto@igalia.com
Subject: [Qemu-devel] [PATCH v3 0/4]
Date: Mon, 12 Oct 2015 19:36:48 -0400 [thread overview]
Message-ID: <cover.1444691409.git.jcody@redhat.com> (raw)
Changes from v2:
Patch 1: Fixed prototype for id_generate() (thanks Alberto)
Used *const instead of * const (thanks Eric, Markus)
Updated function comment (thanks Markus)
Made random in range 0-99 instead of 0-98 (thanks, Marksu)
Patch 2: Cleaned up comments (thanks Markus)
use else if instead of nested if (thanks Markus)
assign node_name on same line as gen_node_name (thanks Markus)
Patch 3,4: new - fix iotests (thanks Kevin)
Changes from RFC v1:
Patch 1: Several typos / grammatical errors (thanks Eric, John)
Make id_subsys_str[] const pointer to const strings (thanks Eric)
Moved id_subsys_str[] out from id_generate() (thanks John)
Assert on null string for given id (thanks Eric)
Zero-pad the 2-digit random # (thanks John)
Patch 2: None
Born from the conversation on qemu-devel, this generation scheme uses the
format ultimately proposed by Kevin, after list discussion.
It attempts to keep the ID strings as small as possible, while fulfilling:
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).
See patch 1 for the generation scheme details.
Jeff Cody (4):
util - add automated ID generation utility
block: auto-generated node-names
block: add filter for generated node-names
qemu-iotests: update tests for generated node-names
block.c | 19 ++++++++++++-------
include/qemu-common.h | 8 ++++++++
tests/qemu-iotests/041 | 4 ++--
tests/qemu-iotests/051 | 3 ++-
tests/qemu-iotests/051.out | 2 +-
tests/qemu-iotests/067 | 3 ++-
tests/qemu-iotests/067.out | 5 +++++
tests/qemu-iotests/081 | 3 ++-
tests/qemu-iotests/081.out | 2 +-
tests/qemu-iotests/common.filter | 5 +++++
util/id.c | 37 +++++++++++++++++++++++++++++++++++++
11 files changed, 77 insertions(+), 14 deletions(-)
--
1.9.3
next reply other threads:[~2015-10-12 23:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 23:36 Jeff Cody [this message]
2015-10-12 23:36 ` [Qemu-devel] [PATCH v3 1/4] util - add automated ID generation utility Jeff Cody
2015-10-13 7:37 ` Markus Armbruster
2015-10-13 11:17 ` Jeff Cody
2015-10-13 15:26 ` Markus Armbruster
2015-10-13 16:40 ` John Snow
2015-10-13 19:25 ` Programmingkid
2015-10-12 23:36 ` [Qemu-devel] [PATCH v3 2/4] block: auto-generated node-names Jeff Cody
2015-10-13 7:39 ` Markus Armbruster
2015-10-12 23:36 ` [Qemu-devel] [PATCH v3 3/4] block: add filter for generated node-names Jeff Cody
2015-10-12 23:36 ` [Qemu-devel] [PATCH v3 4/4] qemu-iotests: update tests " Jeff Cody
2015-10-13 7:41 ` Markus Armbruster
2015-10-13 11:18 ` Jeff Cody
2015-10-13 13:03 ` [Qemu-devel] [PATCH v3 0/4] Kevin Wolf
2015-10-13 15:26 ` 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=cover.1444691409.git.jcody@redhat.com \
--to=jcody@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.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).