From: Or Gerlitz <ogerlitz@Voltaire.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: netdev@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>,
Gregory Haskins <ghaskins@novell.com>
Subject: [Qemu-devel] Re: user space virtio-net exits with "truncating packet" error
Date: Thu, 14 May 2009 15:25:35 +0300 [thread overview]
Message-ID: <4A0C0DBF.3010201@Voltaire.com> (raw)
In-Reply-To: <1242300155.17366.20.camel@blaa>
Mark McLoughlin wrote:
> That sounds like a bug in qemu's mergeable receive buffers
> implementation - the host is running out of buffers for the packet, even
> though it supposedly has already checked that there is enough buffers
> available on the ring.
>
> Hmm, I think I see the bug - does the patch below work? Please try
> several mtu values around the 9k mark to be sure
No, it doesn't help, same crash.
Or.
prev parent reply other threads:[~2009-05-14 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0905141258570.31748@zuben.voltaire.com>
2009-05-14 11:22 ` [Qemu-devel] Re: user space virtio-net exits with "truncating packet" error Mark McLoughlin
2009-05-14 12:25 ` Or Gerlitz [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=4A0C0DBF.3010201@Voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=avi@redhat.com \
--cc=ghaskins@novell.com \
--cc=markmc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=qemu-devel@nongnu.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 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).