From: Rusty Russell <rusty@rustcorp.com.au>
To: virtualization@lists.linux-foundation.org
Cc: Ken Stailey <kstailey@yahoo.com>,
netdev@vger.kernel.org, "Bruce Rogers" <brogers@novell.com>
Subject: Re: [PATCH] virtio-net: add schedule check to napi_enable call in refill_work
Date: Thu, 10 Feb 2011 12:01:19 +1030 [thread overview]
Message-ID: <201102101201.19656.rusty@rustcorp.com.au> (raw)
In-Reply-To: <132885.30568.qm@web110313.mail.gq1.yahoo.com>
On Thu, 10 Feb 2011 06:59:25 am Ken Stailey wrote:
> Justification:
>
> Impact: Under heavy network I/O load virtio-net driver crashes making VM guest unusable.
Hmm, this went badly wrong. I acked this patch, and it was mailed to
netdev six months ago.
Bruce's patch used spaces instead of tabs, but that should not have caused
it to be dropped. I've taken that and ported it forwards, will repost now.
Thanks for picking this up off the floor!
Rusty.
next parent reply other threads:[~2011-02-10 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <132885.30568.qm@web110313.mail.gq1.yahoo.com>
2011-02-10 1:31 ` Rusty Russell [this message]
2011-02-10 2:44 ` [PATCH] virtio-net: add schedule check to napi_enable call in refill_work Bruce Rogers
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=201102101201.19656.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=brogers@novell.com \
--cc=kstailey@yahoo.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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