From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Wangkai (Kevin,C)" <wangkai86@huawei.com>
Cc: Lee yang <lee.yang@huawei.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"aliguori@amazon.com" <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH v2] Tap: fix vcpu long time io blocking on tap
Date: Mon, 28 Jul 2014 16:52:57 +0100 [thread overview]
Message-ID: <20140728155257.GI13872@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <87B246BB5ED53A4C98E4F9A35839EDE128F715AD@nkgeml506-mbs.china.huawei.com>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
On Fri, Jul 18, 2014 at 09:33:42AM +0000, Wangkai (Kevin,C) wrote:
> fix vcpu long time io blocking on tap, when too many packets was delivered
> to the guest os via tap interface.
>
> --
> Signed-off-by: Wangkai <wangkai86@huawei.com>
Thanks, applied to my net-next tree:
https://github.com/stefanha/qemu/commits/net-next
The patch did not apply cleanly so I had to do it manually:
Applying: Tap: fix vcpu long time io blocking on tap
fatal: corrupt patch at line 32
Repository lacks necessary blobs to fall back on 3-way merge.
Cannot fall back to three-way merge.
Patch failed at 0001 Tap: fix vcpu long time io blocking on tap
Please use git-send-email(1).
I also adjusted the commit message and doc comments to fit QEMU style
and for grammar.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-07-28 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 9:33 [Qemu-devel] [PATCH v2] Tap: fix vcpu long time io blocking on tap Wangkai (Kevin,C)
2014-07-28 15:52 ` Stefan Hajnoczi [this message]
2014-07-29 12:02 ` Wangkai (Kevin,C)
2014-07-29 12:43 ` Stefan Hajnoczi
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=20140728155257.GI13872@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=aliguori@amazon.com \
--cc=lee.yang@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wangkai86@huawei.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).