From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Cc: kwolf@redhat.com, Jes.Sorensen@redhat.com,
Alex Williamson <alex.williamson@redhat.com>,
agraf@suse.de, stefanha@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCHv2 0/3] e1000: multi-buffer packet support
Date: Tue, 15 Feb 2011 18:27:44 +0200 [thread overview]
Message-ID: <cover.1297787220.git.mst@redhat.com> (raw)
e1000 supports multi-buffer packets larger than rxbuf_size.
This fixes the following (on linux):
- in guest: ifconfig eth1 mtu 16110
- in host: ifconfig tap0 mtu 16110
ping -s 16082 <guest-ip>
Red Hat bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=602205
Changes from v1:
fix buffer overflow reported by Kevin
added a patch to fix EOP spec violation reported by Juan
added a patch to fix spec violation noted by myself
Michael S. Tsirkin (3):
e1000: multi-buffer packet support
e1000: clear EOP for multi-buffer descriptors
e1000: verify we have buffers, upfront
hw/e1000.c | 61 +++++++++++++++++++++++++++++++++++++++++++++++------------
1 files changed, 48 insertions(+), 13 deletions(-)
--
1.7.3.2.91.g446ac
next reply other threads:[~2011-02-15 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 16:27 Michael S. Tsirkin [this message]
2011-02-15 16:27 ` [Qemu-devel] [PATCHv2 1/3] e1000: multi-buffer packet support Michael S. Tsirkin
2011-02-15 16:27 ` [Qemu-devel] [PATCHv2 2/3] e1000: clear EOP for multi-buffer descriptors Michael S. Tsirkin
2011-02-15 16:27 ` [Qemu-devel] [PATCHv2 3/3] e1000: verify we have buffers, upfront Michael S. Tsirkin
2011-02-16 11:37 ` [Qemu-devel] Re: [PATCHv2 0/3] e1000: multi-buffer packet support Stefan Hajnoczi
2011-02-17 0:05 ` [Qemu-devel] " Alex Williamson
2011-02-17 12:04 ` [Qemu-devel] " Kevin Wolf
2011-02-20 14:29 ` [Qemu-devel] " Aurelien Jarno
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=cover.1297787220.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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.