From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MMLMY-0002Oe-Mw
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 08:26:03 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MMLMT-0002MK-0E
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 08:26:00 -0400
Received: from [199.232.76.173] (port=35987 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MMLMQ-0002Lr-Mw
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 08:25:55 -0400
Received: from fwil.voltaire.com ([193.47.165.2]:53421 helo=exil.voltaire.com)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <ogerlitz@voltaire.com>) id 1MMLMQ-0004Za-8S
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 08:25:54 -0400
Message-ID: <4A4CA747.1050509@Voltaire.com>
Date: Thu, 02 Jul 2009 15:25:43 +0300
From: Or Gerlitz <ogerlitz@Voltaire.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] net: add raw backend
References: <Pine.LNX.4.64.0907011844470.32248@zuben.voltaire.com>
	<20090701162115.GA4555@shareable.org>
In-Reply-To: <20090701162115.GA4555@shareable.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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: Jamie Lokier <jamie@shareable.org>
Cc: Herbert Xu <herbert.xu@redhat.com>, qemu-devel@nongnu.org

Jamie Lokier wrote:
> It looks like it would be functionally identical to the pcap network backend, 
> with the same advantages and problems, but one less dependency on an external
> library (and removes any compatibility with ancient kernels that are in libpcap, 
> but QEMU doesn't work on them anyway).

Assuming that by "pcap network backend" you refer to the -net dump backend, I don't think this (the idea/patch being functionally identical) is the case with the current code: the dump backend opens a file and writes there packets received from the vlan in pcap format, that's all. So first, there's no direct linking with libpcap, and more important, the packets aren't going to the network through the dump backend. With the raw backend, there's no pcap file, but packets are sent to and received from the network through packet socket.

Or.