qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] idea: non-ethernet paravirtual network device
Date: Tue, 26 Jul 2011 12:23:58 +0200	[thread overview]
Message-ID: <4E2E95BE.2070005@suse.de> (raw)
In-Reply-To: <CAJSP0QWQrrRV71sTb3LBq4xj5XyaLFShW4Dn1Rcbn4gzJquimA@mail.gmail.com>

On 07/26/2011 08:04 AM, Stefan Hajnoczi wrote:
> On Mon, Jul 25, 2011 at 4:53 PM, Sassan Panahinejad<sassan@sassan.me.uk>  wrote:
>> Here's a thought, could we improve network performance by creating a
>> paravirtual network device which doesn't emulate ethernet? It shouldn't be
>> too hard to just whack IP packets pretty much directly over a virtio link.
>> This should improve performance when using a "user" host connection and we
>> could introduce a tun host connection instead of tap for this setup.
>>
>> Does anyone have any thoughts on how worthwhile this would be? Would the
>> performance improvement justify the effort involved?
>
> My guess is no noticable impact (if you ignore ARP requests).
>
> The Ethernet header is only 14 bytes or so.  We don't calculate any
> checksums at that level.  There's probably not much of a win.
>
Only lots of pain to be had.
Mainframe used to do this. But abandoned it not, thankfully.

Problem is that you need to patch each and every tool looking at the 
packets to _not_ expecting an Ethernet header.
And patching up DHCP is _not_ trivial.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2011-07-26 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 15:53 [Qemu-devel] idea: non-ethernet paravirtual network device Sassan Panahinejad
2011-07-26  6:04 ` Stefan Hajnoczi
2011-07-26 10:23   ` Hannes Reinecke [this message]
2011-07-26 14:20     ` Sassan Panahinejad

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=4E2E95BE.2070005@suse.de \
    --to=hare@suse.de \
    --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).