From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MEJnq-00059M-Sk
	for qemu-devel@nongnu.org; Wed, 10 Jun 2009 05:09:02 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MEJnm-00057N-1X
	for qemu-devel@nongnu.org; Wed, 10 Jun 2009 05:09:02 -0400
Received: from [199.232.76.173] (port=44541 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MEJnl-00057F-SF
	for qemu-devel@nongnu.org; Wed, 10 Jun 2009 05:08:57 -0400
Received: from mx2.redhat.com ([66.187.237.31]:60729)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <mst@redhat.com>) id 1MEJnk-0001b6-GG
	for qemu-devel@nongnu.org; Wed, 10 Jun 2009 05:08:56 -0400
Date: Wed, 10 Jun 2009 12:07:59 +0300
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20090610090759.GC8614@redhat.com>
References: <20090606204845.GC26877@redhat.com>
	<7162ab20906081201y4c598899mdfd5d42c42e17038@mail.gmail.com>
	<4A2D63EC.9040003@codemonkey.ws>
	<20090608192911.GA32168@redhat.com>
	<4A2D7CB6.5060101@codemonkey.ws> <20090609095701.GC1480@redhat.com>
	<20090609150012.GA3921@shareable.org>
	<4A2E82E8.6050209@siemens.com> <20090610084629.GB8614@redhat.com>
	<4A2F75C4.1010607@siemens.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A2F75C4.1010607@siemens.com>
Subject: [Qemu-devel] Re: [PATCH 6/7] virtio-net: Add new RX filter controls
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: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org, Alex Williamson <alex.williamson@hp.com>

On Wed, Jun 10, 2009 at 10:58:44AM +0200, Jan Kiszka wrote:
> Michael S. Tsirkin wrote:
> > On Tue, Jun 09, 2009 at 05:42:32PM +0200, Jan Kiszka wrote:
> >> The same is true for PF_PACKET (or does libpcap actually use that
> >> internally?). Haven't analyzed the reasons in details yet, but I bet
> >> it's not solvable in user space.
> >>
> >> Jan
> > 
> > I think you can load the veth module, and attach veth to a bridge.
> 
> Sorry, my brain is not yet working at full speed: What do we gain for
> the initial problem that we want to bridge to an existing network device
> without having to move management tools like dhcpcd to the corresponding
> brX?
> 
> Jan

Nothing :). I was only saying that IIUC the problem is not with
PF_PACKET itself - I think that PF_PACKET + veth can be used
as a replacement for tap.

-- 
MST