From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lyqwb-0007gA-S3 for qemu-devel@nongnu.org; Tue, 28 Apr 2009 13:18:09 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LyqwX-0007dS-67 for qemu-devel@nongnu.org; Tue, 28 Apr 2009 13:18:09 -0400 Received: from [199.232.76.173] (port=41061 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LyqwW-0007d6-Br for qemu-devel@nongnu.org; Tue, 28 Apr 2009 13:18:04 -0400 Received: from mx20.gnu.org ([199.232.41.8]:42797) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LyqwU-0000PR-M0 for qemu-devel@nongnu.org; Tue, 28 Apr 2009 13:18:03 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LyqwT-0008OG-64 for qemu-devel@nongnu.org; Tue, 28 Apr 2009 13:18:01 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Re: [PATCH 9/9] Introduce VLANClientState::cleanup() Date: Tue, 28 Apr 2009 18:17:55 +0100 References: <1239812969-8320-2-git-send-email-markmc@redhat.com> <200904281308.26203.paul@codesourcery.com> <49F732F4.6020708@codemonkey.ws> In-Reply-To: <49F732F4.6020708@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904281817.56416.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Mark McLoughlin , Anthony Liguori , Marcelo Tosatti , Markus Armbruster > 1) Network backend is created. As part of the configuration of the > backend, a unique device identifier is associated with it. > 2) A PCI device is created. > a) The PCI device creates one or more Network frontends. Each > frontend carries the device identifier and perhaps something like a port > id. b) When the PCI device is destroyed, it destroys any frontends it owns. This sounds about right, though I'm not entirely sure what you mean by "network backend". backend ~= vlan in the current implementation? Paul