From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50027) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZlzFO-0000IM-U5 for qemu-devel@nongnu.org; Tue, 13 Oct 2015 09:04:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZlzFO-0005nl-57 for qemu-devel@nongnu.org; Tue, 13 Oct 2015 09:04:06 -0400 Date: Tue, 13 Oct 2015 15:03:58 +0200 From: Kevin Wolf Message-ID: <20151013130358.GJ4906@noname.str.redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v3 0/4] List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jeff Cody Cc: qemu-block@nongnu.org, jsnow@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com, programmingkidx@gmail.com, berto@igalia.com Am 13.10.2015 um 01:36 hat Jeff Cody geschrieben: > 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. Thanks, squashed patches 2-4 and applied to the block branch. Kevin