From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58987) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aw9KZ-0001ms-7V for qemu-devel@nongnu.org; Fri, 29 Apr 2016 10:23:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aw9KN-0002Iv-P4 for qemu-devel@nongnu.org; Fri, 29 Apr 2016 10:23:37 -0400 Date: Fri, 29 Apr 2016 16:22:54 +0200 From: Kevin Wolf Message-ID: <20160429142254.GF4350@noname.redhat.com> References: <2c95dbf66898b364e5f3ef134af279fa7ce113c0.1459776815.git.berto@igalia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2c95dbf66898b364e5f3ef134af279fa7ce113c0.1459776815.git.berto@igalia.com> Subject: Re: [Qemu-devel] [PATCH v9 01/11] block: keep a list of block jobs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alberto Garcia Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, Max Reitz , Eric Blake , Stefan Hajnoczi Am 04.04.2016 um 15:43 hat Alberto Garcia geschrieben: > The current way to obtain the list of existing block jobs is to > iterate over all root nodes and check which ones own a job. > > Since we want to be able to support block jobs in other nodes as well, > this patch keeps a list of jobs that is updated every time one is > created or destroyed. > > Signed-off-by: Alberto Garcia Reviewed-by: Kevin Wolf Actually, I have almost literally the same change (except that I didn't need a block_job_next()) in my development branch. I guess I should rebase on top of this one. :-) Kevin