From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm@vger.kernel.org, Mark McLoughlin <markmc@redhat.com>
Subject: Re: [PATCH] Use guards in virtio-net for easier upstream merging (v2)
Date: Fri, 05 Dec 2008 19:40:59 +0200 [thread overview]
Message-ID: <493967AB.7090406@redhat.com> (raw)
In-Reply-To: <1228403617-13389-1-git-send-email-aliguori@us.ibm.com>
Anthony Liguori wrote:
> This gets virtio-net into an upstream acceptable state. This includes
> introducing USE_KVM guards for IO thread notification (where did
> qemu_service_io() go?). It also includes introducing TAP_VNET_HDR which is for
> code that relies on the tap vnet support that is not currently in upstream QEMU.
>
> Finally, it drops packets if not ready to receive. This is unnecessary in
> kvm-userspace but necessary in QEMU.
>
> Since v1, I enable tap vnet by default, and pass the buffer size to
> virtio_net_receive() as suggested by Mark.
>
Applied, thanks.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2008-12-05 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 15:13 [PATCH] Use guards in virtio-net for easier upstream merging (v2) Anthony Liguori
2008-12-05 17:40 ` Avi Kivity [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=493967AB.7090406@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.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).