From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH net-next V2 0/3] rx busy polling support for virtio-net
Date: Mon, 21 Jul 2014 11:15:00 +0800 [thread overview]
Message-ID: <53CC85B4.8070203@redhat.com> (raw)
In-Reply-To: <20140720203417.GF2536@redhat.com>
On 07/21/2014 04:34 AM, Michael S. Tsirkin wrote:
> On Wed, Jul 16, 2014 at 02:21:44PM +0800, Jason Wang wrote:
>> Hi all:
>>
>> This series introduces the support for rx busy polling support. This
>> was useful for reduing the latency for a kvm guest. Patch 1-2
>> introduces helpers which is used for rx busy polling. Patch 3
>> implement the main function.
>>
>> Test was done between a kvm guest and an external host. Two hosts were
>> connected through 40gb mlx4 cards. With both busy_poll and busy_read are
>> set to 50 in guest, 1 byte netperf tcp_rr shows 116% improvement:
>> transaction rate was increased from 9151.94 to 19787.37.
>>
>> Changes from V1:
>> - split the patch info smaller ones
>> - add more details about test setup/configuration
>>
>> Please review.
> Generally I think we should let host know we are polling.
> For example, kick the rq or something. Or maybe add another
> io address.
Yes, I'm also working on busy polling for tun and vhost which may also
help here.
> Something like this would need a new feature flag though, so I'm fine
> with just polling in guest until that is available.
Yes.
>
>> Jason Wang (3):
>> virtio-net: introduce helpers to enable and disable all NAPIs
>> virtio-net: introduce virtnet_receive()
>> virtio-net: rx busy polling support
>>
>> drivers/net/virtio_net.c | 234 ++++++++++++++++++++++++++++++++++++++++++++---
>> 1 file changed, 221 insertions(+), 13 deletions(-)
>>
>> --
>> 1.8.3.1
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
WARNING: multiple messages have this Message-ID (diff)
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: rusty@rustcorp.com.au, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next V2 0/3] rx busy polling support for virtio-net
Date: Mon, 21 Jul 2014 11:15:00 +0800 [thread overview]
Message-ID: <53CC85B4.8070203@redhat.com> (raw)
In-Reply-To: <20140720203417.GF2536@redhat.com>
On 07/21/2014 04:34 AM, Michael S. Tsirkin wrote:
> On Wed, Jul 16, 2014 at 02:21:44PM +0800, Jason Wang wrote:
>> Hi all:
>>
>> This series introduces the support for rx busy polling support. This
>> was useful for reduing the latency for a kvm guest. Patch 1-2
>> introduces helpers which is used for rx busy polling. Patch 3
>> implement the main function.
>>
>> Test was done between a kvm guest and an external host. Two hosts were
>> connected through 40gb mlx4 cards. With both busy_poll and busy_read are
>> set to 50 in guest, 1 byte netperf tcp_rr shows 116% improvement:
>> transaction rate was increased from 9151.94 to 19787.37.
>>
>> Changes from V1:
>> - split the patch info smaller ones
>> - add more details about test setup/configuration
>>
>> Please review.
> Generally I think we should let host know we are polling.
> For example, kick the rq or something. Or maybe add another
> io address.
Yes, I'm also working on busy polling for tun and vhost which may also
help here.
> Something like this would need a new feature flag though, so I'm fine
> with just polling in guest until that is available.
Yes.
>
>> Jason Wang (3):
>> virtio-net: introduce helpers to enable and disable all NAPIs
>> virtio-net: introduce virtnet_receive()
>> virtio-net: rx busy polling support
>>
>> drivers/net/virtio_net.c | 234 ++++++++++++++++++++++++++++++++++++++++++++---
>> 1 file changed, 221 insertions(+), 13 deletions(-)
>>
>> --
>> 1.8.3.1
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2014-07-21 3:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 6:21 [PATCH net-next V2 0/3] rx busy polling support for virtio-net Jason Wang
2014-07-16 6:21 ` Jason Wang
2014-07-16 6:21 ` [PATCH net-next V2 1/3] virtio-net: introduce helpers to enable and disable all NAPIs Jason Wang
2014-07-16 6:21 ` Jason Wang
2014-07-16 6:21 ` [PATCH net-next V2 2/3] virtio-net: introduce virtnet_receive() Jason Wang
2014-07-16 6:21 ` Jason Wang
2014-07-16 6:21 ` [PATCH net-next V2 3/3] virtio-net: rx busy polling support Jason Wang
2014-07-16 6:21 ` Jason Wang
2014-07-16 8:38 ` Varka Bhadram
2014-07-17 2:55 ` Jason Wang
2014-07-17 3:27 ` Varka Bhadram
2014-07-17 4:43 ` Jason Wang
2014-07-17 4:54 ` Varka Bhadram
2014-07-20 20:31 ` Michael S. Tsirkin
2014-07-20 20:31 ` Michael S. Tsirkin
2014-07-21 3:13 ` Jason Wang
2014-07-21 3:13 ` Jason Wang
2014-07-17 6:21 ` [PATCH net-next V2 0/3] rx busy polling support for virtio-net David Miller
2014-07-17 6:21 ` David Miller
2014-07-17 6:59 ` Jason Wang
2014-07-17 6:59 ` Jason Wang
2014-07-20 20:34 ` Michael S. Tsirkin
2014-07-20 20:34 ` Michael S. Tsirkin
2014-07-21 3:15 ` Jason Wang [this message]
2014-07-21 3:15 ` Jason Wang
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=53CC85B4.8070203@redhat.com \
--to=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@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.