From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1N661B-0000Y7-06
	for qemu-devel@nongnu.org; Thu, 05 Nov 2009 12:21:05 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1N6616-0000XI-0x
	for qemu-devel@nongnu.org; Thu, 05 Nov 2009 12:21:04 -0500
Received: from [199.232.76.173] (port=59677 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1N6615-0000XC-QO
	for qemu-devel@nongnu.org; Thu, 05 Nov 2009 12:20:59 -0500
Received: from moutng.kundenserver.de ([212.227.126.177]:53765)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <arnd@arndb.de>) id 1N6614-00086N-M8
	for qemu-devel@nongnu.org; Thu, 05 Nov 2009 12:20:59 -0500
From: Arnd Bergmann <arnd@arndb.de>
Subject: Re: [Qemu-devel] [PATCH 0/4] net-bridge: rootless bridge support for
	qemu
Date: Thu, 5 Nov 2009 18:20:48 +0100
References: <1257294485-27015-1-git-send-email-aliguori@us.ibm.com>
	<20091105163702.GC21630@shareable.org>
	<4AF30129.7080203@us.ibm.com>
In-Reply-To: <4AF30129.7080203@us.ibm.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200911051820.48878.arnd@arndb.de>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Mark McLoughlin <markmc@redhat.com>, Arnd Bergmann <arndbergmann@googlemail.com>, Juan Quintela <quintela@redhat.com>, Dustin Kirkland <kirkland@canonical.com>, qemu-devel@nongnu.org, Michael Tsirkin <mst@redhat.com>, Avi Kivity <avi@redhat.com>

On Thursday 05 November 2009, Anthony Liguori wrote:
> > It'd still install the default helper you've provided and use it by
> > default, of course.
> >   
> That's already how it behaves.  You can say -net 
> bridge,helper=/usr/local/bin/my-helper
> 

How about abstracting it further and not making the helper depend on
bridge code. If we put the helper into netcf, we could make that
a more generic '-net netcf,helper=/usr/bin/netcf-helper' target,
with netcf doing the correct thing for the system configuration,
whether that is tap+bridge, tap+route, macvtap or something else
coming up. The helper would essentially become a black box for
providing a tap-like file descriptor with external connectivity.

	Arnd <><