From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N6ENh-0007SY-Fg for qemu-devel@nongnu.org; Thu, 05 Nov 2009 21:16:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N6ENc-0007Je-PX for qemu-devel@nongnu.org; Thu, 05 Nov 2009 21:16:53 -0500 Received: from [199.232.76.173] (port=38642 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N6ENc-0007JS-L2 for qemu-devel@nongnu.org; Thu, 05 Nov 2009 21:16:48 -0500 Received: from mx20.gnu.org ([199.232.41.8]:14848) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1N6ENc-0001pY-BG for qemu-devel@nongnu.org; Thu, 05 Nov 2009 21:16:48 -0500 Received: from mail2.shareable.org ([80.68.89.115]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N6ENb-0006iJ-NG for qemu-devel@nongnu.org; Thu, 05 Nov 2009 21:16:47 -0500 Date: Fri, 6 Nov 2009 02:16:45 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH 0/4] net-bridge: rootless bridge support for qemu Message-ID: <20091106021645.GK21630@shareable.org> References: <4AF2E247.3090409@redhat.com> <4AF2E7CE.8010506@us.ibm.com> <4AF2EB17.8090202@redhat.com> <4AF2F7E9.50300@us.ibm.com> <4AF2FA2A.4060500@redhat.com> <4AF2FC88.5030303@us.ibm.com> <4AF2FE57.2080700@redhat.com> <4AF30255.2020303@us.ibm.com> <4AF31747.4070806@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AF31747.4070806@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Mark McLoughlin , Anthony Liguori , Arnd Bergmann , Scott Tsai , Dustin Kirkland , Juan Quintela , qemu-devel@nongnu.org, Michael Tsirkin Avi Kivity wrote: > On 11/05/2009 07:16 PM, Scott Tsai wrote: > >On Fri, Nov 6, 2009 at 12:50 AM, Anthony Liguori > >wrote: > > > >>It's just a bit annoying to create an entire new > >>project for a few hundred line helper. > >> > >This new project would also be a better place for 'tunctl' and other > >projects such as user mode linux might want to use your new helper > >program. > > > > Seems like a library implemented as executables instead of a shared object. Yes. It's an executable because it needs setuid to do privileged things... It could be provided as a shared object (which calls an executable if it needs setuiding), but then for some things you'd have to provide an option like -net helper=/path/to/my/helper.so, and you might not want the implied fixed ABI, and it'd be harder to use scripts. After all we don't have -net script=/path/to/my/upscript.so,downscript=/path/to/my/downscript.so do we? ;-) Spawning an executable is really fast in Linux. For something which is only called a few times at most when the program starts or is rarely reconfigured, I don't see any reason not to call an executable. -- Jamie