All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Mark McLoughlin <markmc@redhat.com>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/1] qemu-kvm: virtio-net: Re-instate GSO code removed upstream
Date: Wed, 30 Sep 2009 15:55:33 +0200	[thread overview]
Message-ID: <4AC36355.8040908@redhat.com> (raw)
In-Reply-To: <20090930135144.GA29956@infradead.org>

On 09/30/2009 03:51 PM, Christoph Hellwig wrote:
> I might sound like a broken record, but why isn't the full GSO support
> for virtio-net upstream in qemu?
>    

IIRC the current hacks are not upstream quality.

The problem (again IIRC) is that the guest and host negotiate a 
protocol, but the qemu vlan model doesn't have a guest and a host, it 
has peers (possibly more than two), so a lot of translation has to take 
place if you have one peer supporting a guest feature and another not.

IMO the best way out is to drop the vlan model.  It has its uses, but 
they can all be implemented in other ways, and are all have minor usage 
compared to the business of getting data into and out of a guest.

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Mark McLoughlin <markmc@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH 1/1] qemu-kvm: virtio-net: Re-instate GSO code removed upstream
Date: Wed, 30 Sep 2009 15:55:33 +0200	[thread overview]
Message-ID: <4AC36355.8040908@redhat.com> (raw)
In-Reply-To: <20090930135144.GA29956@infradead.org>

On 09/30/2009 03:51 PM, Christoph Hellwig wrote:
> I might sound like a broken record, but why isn't the full GSO support
> for virtio-net upstream in qemu?
>    

IIRC the current hacks are not upstream quality.

The problem (again IIRC) is that the guest and host negotiate a 
protocol, but the qemu vlan model doesn't have a guest and a host, it 
has peers (possibly more than two), so a lot of translation has to take 
place if you have one peer supporting a guest feature and another not.

IMO the best way out is to drop the vlan model.  It has its uses, but 
they can all be implemented in other ways, and are all have minor usage 
compared to the business of getting data into and out of a guest.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-09-30 13:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 16:50 virtio-net not working with the latest qemu-kvm git Sridhar Samudrala
2009-05-04 17:44 ` Alex Williamson
2009-05-05  8:56   ` [PATCH 1/1] qemu-kvm: virtio-net: Re-instate GSO code removed upstream Mark McLoughlin
2009-05-06  9:11     ` Avi Kivity
2009-09-29 20:45     ` Mark McLoughlin
2009-09-29 20:47       ` Mark McLoughlin
2009-09-30  6:24       ` Avi Kivity
2009-09-30 11:24         ` Glauber Costa
2009-09-30 11:24           ` Mark McLoughlin
2009-09-30 13:01         ` Anthony Liguori
2009-09-30 13:51       ` Christoph Hellwig
2009-09-30 13:51         ` [Qemu-devel] " Christoph Hellwig
2009-09-30 13:55         ` Avi Kivity [this message]
2009-09-30 13:55           ` Avi Kivity
2009-09-30 13:59           ` Mark McLoughlin
2009-09-30 13:59             ` [Qemu-devel] " Mark McLoughlin
2009-09-30 19:15             ` Gerd Hoffmann
2009-09-30 19:15               ` [Qemu-devel] " Gerd Hoffmann
2009-10-01  6:59               ` Mark McLoughlin
2009-10-01 16:49             ` Avi Kivity
2009-10-01 16:49               ` [Qemu-devel] " Avi Kivity
2009-10-01 17:00               ` Mark McLoughlin
2009-10-01 17:00                 ` [Qemu-devel] " Mark McLoughlin
2009-10-01 17:04                 ` Avi Kivity
2009-10-01 17:04                   ` [Qemu-devel] " Avi Kivity
2009-05-05  8:56   ` virtio-net not working with the latest qemu-kvm git Mark McLoughlin
2009-05-06  9:12 ` Avi Kivity

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=4AC36355.8040908@redhat.com \
    --to=avi@redhat.com \
    --cc=hch@infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.