From: "Michael S. Tsirkin" <mst@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: network performance degradation in virtio_net in 4.12-rc
Date: Mon, 22 May 2017 20:42:10 +0300 [thread overview]
Message-ID: <20170522203532-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <alpine.LRH.2.02.1705221003450.20076@file01.intranet.prod.int.rdu2.redhat.com>
On Mon, May 22, 2017 at 10:25:19AM -0400, Mikulas Patocka wrote:
> Hi
>
> I see severe network performance degradation with the kernels 4.12-rc1 and
> 4.12-rc2 in the network virtio driver. Download rate drops down to about
> 100kB/s.
>
> I bisected it and it is caused by patch
> d85b758f72b05a774045545f24d70980e3e9aac4 ("virtio_net: fix support for
> small rings"). When I revert this patch, the problem goes away.
>
> The host is Debian Jessie with kernel 4.4.62, the guest is Debian Sid with
> kernel 4.12-rc.
>
> Mikulas
Thanks for the report!
I'm not sure what causes it on this host. I'll try to reproduce.
Meanwhile, could you please locate this line of code:
+ vi->rq[i].min_buf_len = mergeable_min_buf_len(vi, vi->rq[i].vq);
and add something like
printk(KERN_ERR, "min buf = 0x%x expected 0x%x size 0x%x big %d\n",
vi->rq[i].min_buf_len, GOOD_PACKET_LEN,
virtqueue_get_vring_size(vi->rq[i].vq),
(int)vi->big_packets);
after it?
Then boot and capture the output.
Thanks!
--
MST
next prev parent reply other threads:[~2017-05-22 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 14:25 network performance degradation in virtio_net in 4.12-rc Mikulas Patocka
2017-05-22 17:42 ` Michael S. Tsirkin [this message]
2017-05-22 21:50 ` Mikulas Patocka
2017-05-22 17:42 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2017-05-22 14:25 Mikulas Patocka
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=20170522203532-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mpatocka@redhat.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 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.