From: Avi Kivity <avi@redhat.com>
To: Bruce Rogers <brogers@novell.com>
Cc: "stable."@kernel.org, kvm@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 0/3][STABLE] KVM: Various issues in virtio_net
Date: Sun, 06 Jun 2010 16:17:14 +0300 [thread overview]
Message-ID: <4C0B9FDA.2090203@redhat.com> (raw)
In-Reply-To: <4C07AE9F020000480009747F@sinclair.provo.novell.com>
On 06/03/2010 10:31 PM, Bruce Rogers wrote:
> These are patches which we have found useful for our 2.6.32 based SLES 11 SP1 release.
>
> The first patch is already upstream, but should be included in stable.
>
> The second patch is a subset of another upstream patch. Again, stable material.
>
> The third patch solves the last remaining issue we saw when testing kvm configurations with the SUSE certification test suite. Under heavy load, we observed rx stalls (first two patches applied), and this third patch was crafted to address the issue. Please apply to stable.
> I assume this last problem also exists in more recent kernels than 2.6.32, but I haven't validated that.
>
> With these 3 patches applied we no longer see any issues with virito networking using our certification test suite.
>
>
Please send virtio patches, including patches for the stable branches,
to the virtio maintainer (Rusty). Copying Michael (mst@redhat.com) is
also a good idea.
Also:
- use git format-patch/git sent-email or equivalents; these ensure the
correct formatting and group the patches together for threaded mail clients
- indicate the upstream commit (often it's enough to ask the maintainers
to backport a commit)
--
error compiling committee.c: too many arguments to function
next parent reply other threads:[~2010-06-06 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C07AE9F020000480009747F@sinclair.provo.novell.com>
2010-06-06 13:17 ` Avi Kivity [this message]
2010-06-03 19:32 [PATCH 0/3][STABLE] KVM: Various issues in virtio_net 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=4C0B9FDA.2090203@redhat.com \
--to=avi@redhat.com \
--cc="stable."@kernel.org \
--cc=brogers@novell.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
/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