From: Jason Wang <jasowang@redhat.com> To: mst@redhat.com, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Jason Wang <jasowang@redhat.com> Subject: [PATCH net-next V2 0/3] vhost net tx batching Date: Wed, 28 Dec 2016 16:09:28 +0800 [thread overview] Message-ID: <1482912571-3157-1-git-send-email-jasowang@redhat.com> (raw) Hi: This series tries to implement tx batching support for vhost. This was done by using MSG_MORE as a hint for under layer socket. The backend (e.g tap) can then batch the packets temporarily in a list and submit it all once the number of bacthed exceeds a limitation. Tests shows obvious improvement on guest pktgen over over mlx4(noqueue) on host: Mpps -+% rx_batched=0 0.90 +0% rx_batched=4 0.97 +7.8% rx_batched=8 0.97 +7.8% rx_batched=16 0.98 +8.9% rx_batched=32 1.03 +14.4% rx_batched=48 1.09 +21.1% rx_batched=64 1.02 +13.3% Changes from V1: - drop NAPI handler since we don't use NAPI now - fix the issues that may exceeds max pending of zerocopy - more improvement on available buffer detection - move the limitation of batched pacekts from vhost to tuntap Please review. Thanks Jason Wang (3): vhost: better detection of available buffers vhost_net: tx batching tun: rx batching drivers/net/tun.c | 66 ++++++++++++++++++++++++++++++++++++++++++++------- drivers/vhost/net.c | 23 +++++++++++++++--- drivers/vhost/vhost.c | 8 +++++-- 3 files changed, 84 insertions(+), 13 deletions(-) -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Jason Wang <jasowang@redhat.com> To: mst@redhat.com, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH net-next V2 0/3] vhost net tx batching Date: Wed, 28 Dec 2016 16:09:28 +0800 [thread overview] Message-ID: <1482912571-3157-1-git-send-email-jasowang@redhat.com> (raw) Hi: This series tries to implement tx batching support for vhost. This was done by using MSG_MORE as a hint for under layer socket. The backend (e.g tap) can then batch the packets temporarily in a list and submit it all once the number of bacthed exceeds a limitation. Tests shows obvious improvement on guest pktgen over over mlx4(noqueue) on host: Mpps -+% rx_batched=0 0.90 +0% rx_batched=4 0.97 +7.8% rx_batched=8 0.97 +7.8% rx_batched=16 0.98 +8.9% rx_batched=32 1.03 +14.4% rx_batched=48 1.09 +21.1% rx_batched=64 1.02 +13.3% Changes from V1: - drop NAPI handler since we don't use NAPI now - fix the issues that may exceeds max pending of zerocopy - more improvement on available buffer detection - move the limitation of batched pacekts from vhost to tuntap Please review. Thanks Jason Wang (3): vhost: better detection of available buffers vhost_net: tx batching tun: rx batching drivers/net/tun.c | 66 ++++++++++++++++++++++++++++++++++++++++++++------- drivers/vhost/net.c | 23 +++++++++++++++--- drivers/vhost/vhost.c | 8 +++++-- 3 files changed, 84 insertions(+), 13 deletions(-) -- 2.7.4
next reply other threads:[~2016-12-28 8:09 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-12-28 8:09 Jason Wang [this message] 2016-12-28 8:09 ` [PATCH net-next V2 0/3] vhost net tx batching Jason Wang 2016-12-28 8:09 ` [PATCH net-next V2 1/3] vhost: better detection of available buffers Jason Wang 2016-12-28 8:09 ` Jason Wang 2017-01-03 13:08 ` Stefan Hajnoczi 2017-01-03 13:08 ` Stefan Hajnoczi 2016-12-28 8:09 ` [PATCH net-next V2 2/3] vhost_net: tx batching Jason Wang 2016-12-28 8:09 ` Jason Wang 2017-01-03 13:16 ` Stefan Hajnoczi 2017-01-03 13:16 ` Stefan Hajnoczi 2016-12-28 8:09 ` [PATCH net-next V2 3/3] tun: rx batching Jason Wang 2016-12-28 8:09 ` Jason Wang 2016-12-29 16:35 ` David Miller 2016-12-29 16:35 ` David Miller 2016-12-30 5:14 ` Jason Wang 2016-12-30 5:14 ` Jason Wang 2017-01-03 13:33 ` Stefan Hajnoczi 2017-01-03 13:33 ` Stefan Hajnoczi 2017-01-04 3:03 ` Jason Wang 2017-01-04 3:03 ` Jason Wang 2017-01-05 9:27 ` Stefan Hajnoczi 2017-01-05 9:27 ` Stefan Hajnoczi
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=1482912571-3157-1-git-send-email-jasowang@redhat.com \ --to=jasowang@redhat.com \ --cc=kvm@vger.kernel.org \ --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: linkBe 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.