From: Stefan Hajnoczi <stefanha@redhat.com>
To: Vincenzo Maffione <v.maffione@gmail.com>
Cc: mst@redhat.com, qemu-devel@nongnu.org, anthony@codemonkey.ws,
pbonzini@redhat.com, g.lettieri@iet.unipi.it, rizzo@iet.unipi.it,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v3] e1000: NetClientInfo.receive_iov implemented
Date: Thu, 12 Sep 2013 15:06:34 +0200 [thread overview]
Message-ID: <20130912130634.GD18070@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1378975657-5141-1-git-send-email-v.maffione@gmail.com>
On Thu, Sep 12, 2013 at 10:47:37AM +0200, Vincenzo Maffione wrote:
> This patch implements the NetClientInfo.receive_iov method for the
> e1000 device emulation. In this way a network backend that uses
> qemu_sendv_packet() can deliver the fragmented packet without
> requiring an additional copy in the frontend/backend network code
> (nc_sendv_compat() function).
>
> The existing method NetClientInfo.receive has been reimplemented
> using the new method.
>
> Signed-off-by: Vincenzo Maffione <v.maffione@gmail.com>
> ---
> hw/net/e1000.c | 70 ++++++++++++++++++++++++++++++++++++++++++++++++----------
> 1 file changed, 58 insertions(+), 12 deletions(-)
>
> I propose this patch also because our research group (University of Pisa,
> Department of Computer Engineering) is working on the e1000 device
> (optimizations and paravirtual extensions) and we have patches to
> support the VALE switch as a network backend (see
> http://info.iet.unipi.it/~luigi/vale/).
> The VALE backend uses qemu_sendv_packet() to send fragmented packets: For
> this reason we think it could be interesting to better support these packets
> with e1000.
Thanks, applied to my net-next tree:
https://github.com/stefanha/qemu/commits/net-next
Stefan
prev parent reply other threads:[~2013-09-12 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 8:47 [Qemu-devel] [PATCH v3] e1000: NetClientInfo.receive_iov implemented Vincenzo Maffione
2013-09-12 13:06 ` Stefan Hajnoczi [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=20130912130634.GD18070@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=g.lettieri@iet.unipi.it \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rizzo@iet.unipi.it \
--cc=v.maffione@gmail.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 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).