From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: performance regression in virtio-net in 2.6.32-rc4
Date: Tue, 27 Oct 2009 11:41:25 +0200 [thread overview]
Message-ID: <4AE6C045.1070800@redhat.com> (raw)
In-Reply-To: <20091026184835.GB26473@redhat.com>
On 10/26/2009 08:48 PM, Michael S. Tsirkin wrote:
> Hi!
> I noticed a performance regression in virtio net: going from
> 2.6.31 to 2.6.32-rc4 I see this, for guest to host communication:
>
> Any tips on debugging this?
>
Lacking better advice, a bisect can help as a last resort. 'git bisect
start -- drivers/net drivers/virtio' will probably find it fastest.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-10-27 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 18:48 performance regression in virtio-net in 2.6.32-rc4 Michael S. Tsirkin
2009-10-27 9:41 ` Avi Kivity
2009-10-27 9:41 ` Avi Kivity [this message]
2009-10-27 23:34 ` Rusty Russell
2009-10-27 23:34 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2009-10-26 18:48 Michael S. Tsirkin
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=4AE6C045.1070800@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.