qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jbrown106@phreaker.net>
To: Mike Tremoulet <coffeemike@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] pcap-based networking?
Date: Thu, 26 Aug 2004 13:33:08 -0400	[thread overview]
Message-ID: <20040826173308.GA1778@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <5640213304082609425986326c@mail.gmail.com>

On Thu, Aug 26, 2004 at 11:42:45AM -0500, Mike Tremoulet wrote:
> All --
> 
> My question is:  Is there a reason to use (or not to use) a
> libpcap/libnet solution for networking?  At a high level, I think of
> it as a queue of incoming packets and a queue of outgoing packets
> (from the standpoint of the guest).  Outgoing packets from the guest
> would be held in a queue and written onto the network via libnet, and
> incoming packets would get captured by libpcap and written to the
> virtual device.
> 
> The advantages for me would be:
> - I can bind this networking to the device of my explicit choosing at
> runtime.  So, I could install a tap device on my host and have qemu
> always use that device, or I could bind it to a second NIC on the
> host.
> - More importantly, this can be somewhat platform independant. 
> Libpcap exists in a very similar, if not identical, API in the form of
> winpcap.  I know there is an equivalent way to write packets to the
> network, but I forget the name right now.
> 
> What would the potential performance impacts be?  Is this something
> that I/we should pursue?  Other thoughts?
> 
> -- Mike

This is a good idea. We should keep the tuntap interface, but adding support
for libpcap is useful for those OSes which do not have a tuntap-like interface.

> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

      parent reply	other threads:[~2004-08-26 17:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 16:42 [Qemu-devel] pcap-based networking? Mike Tremoulet
2004-08-26 17:15 ` John R. Hogerhuis
2004-08-26 17:19   ` Mike Tremoulet
2004-08-26 17:48     ` John R. Hogerhuis
2004-08-27  6:08       ` Mike Tremoulet
2004-08-27  6:28         ` John R. Hogerhuis
2004-08-27  6:32           ` Mike Tremoulet
2004-08-26 17:33 ` Jim C. Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040826173308.GA1778@jbrown.mylinuxbox.org \
    --to=jbrown106@phreaker.net \
    --cc=coffeemike@gmail.com \
    --cc=jbrown106@swift-mail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).