From: Or Gerlitz <ogerlitz@Voltaire.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Avi Kivity <avi@redhat.com>,
netdev@vger.kernel.org, Gregory Haskins <ghaskins@novell.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: user space virtio-net exits with "truncating packet" error
Date: Thu, 14 May 2009 17:04:48 +0300 [thread overview]
Message-ID: <4A0C2500.7090709@Voltaire.com> (raw)
In-Reply-To: <200905142128.58111.rusty@rustcorp.com.au>
Rusty Russell wrote:
> The answer is that virtio_net by default only supports 1500
> MTU; I've not tried larger MTUs.
Rusty,
I hoped to get some performance boost from using checksum and large-send offloads
as an alternative to jumbo frames. Looking in the virtio-net kernel driver, I see that the probe
function checks if virtio_has_feature VIRTIO_NET_F_CSUM ... VIRTIO_NET_F_HOST_TSO ... and if yes
sets the relevant bits in the NIC features mask. Looking in the virtio qemu code, I also see some offload
related code.
In my case, both the guest and the host run 2.6.29.1 and I use ethX (igb based) -- bridge -- tapY <--> qemu configuration, where qemu is the one provided by kvm latest release (84). Now, the virtio guest NIC doesn't expose any features (its mask being 0x20 - only highdma). Anything I can do to have offloads support for my virtio environment?
Or.
next prev parent reply other threads:[~2009-05-14 14:04 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 [this message]
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
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=4A0C2500.7090709@Voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=ghaskins@novell.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.