From: Rusty Russell <rusty@rustcorp.com.au>
To: Or Gerlitz <ogerlitz@voltaire.com>
Cc: Avi Kivity <avi@redhat.com>,
netdev@vger.kernel.org, Gregory Haskins <ghaskins@novell.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Mark McLoughlin <markmc@redhat.com>
Subject: Re: user space virtio-net exits with "truncating packet" error
Date: Thu, 21 May 2009 15:23:05 +0930 [thread overview]
Message-ID: <200905211523.07278.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4A13A127.30305@voltaire.com>
On Wed, 20 May 2009 03:50:23 pm Or Gerlitz wrote:
> Rusty Russell wrote:
> > Bit 5 = VIRTIO_NET_F_MAC (the host set the mac address)
> > Bit 24 = VIRTIO_F_NOTIFY_ON_EMPTY
> > You don't have any GSO or checksum offload here
>
> Just to make sure I'm in the correct direction - I need to cause these
> offloads to be advertised by the "lower" part of virtio (e.g the qemu
> virtio code) to the "upper" part (the quest kernel), correct? I
> understand that one of them is called front-end and the other back-end,
> but my intuitions don't go up to saying who's what...
Yes, that nomenclature is a bit weird. I prefer "driver" (aka. guest, aka
front-end) and "device" (aka. host, aka back-end).
All virtio_net drivers offer some features (at least CSUM offload), and 2.6.26
and above will offer some serious GSO features.
Cheers,
Rusty.
next prev parent reply other threads:[~2009-05-21 5:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 10:07 user space virtio-net exits with "truncating packet" error Or Gerlitz
2009-05-14 11:22 ` Mark McLoughlin
2009-05-14 11:22 ` [Qemu-devel] " Mark McLoughlin
2009-05-14 12:25 ` Or Gerlitz
2009-05-14 12:25 ` [Qemu-devel] " Or Gerlitz
2009-05-14 11:58 ` Rusty Russell
2009-05-14 14:04 ` Or Gerlitz
2009-05-14 18:04 ` Or Gerlitz
2009-05-15 5:18 ` Rusty Russell
2009-05-19 12:19 ` Or Gerlitz
2009-05-20 2:47 ` Rusty Russell
2009-05-20 6:20 ` Or Gerlitz
2009-05-20 6:59 ` Avi Kivity
2009-05-21 5:53 ` Rusty Russell [this message]
2009-05-15 7:07 ` Michael Tokarev
2009-05-19 10:00 ` Or Gerlitz
2009-05-19 10:13 ` Avi Kivity
2009-05-14 15:34 ` Sridhar Samudrala
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=200905211523.07278.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=ghaskins@novell.com \
--cc=markmc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.com \
/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.