netdev - Re: [PATCH v3 net-next 0/2] rx busy polling support for virtio-net

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 23 Jul 2014 15:12:52 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jasowang@...hat.com
Cc:	rusty@...tcorp.com.au, mst@...hat.com,
	virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 net-next 0/2] rx busy polling support for virtio-net

From: Jason Wang <jasowang@...hat.com>
Date: Wed, 23 Jul 2014 16:33:53 +0800

> This series introduces the support for rx busy polling support. This
> was useful for reduing the latency for a kvm guest. Instead of
> introducing new states and spinlocks, this series re-uses NAPI state
> to synchonrize between NAPI and busy polling. This grealy simplified
> the codes and reduce the overheads of spinlocks for normal NAPI fast
> path.
> 
> 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 127% improvement:
> transaction rate was increased from 8353.33 to 18966.87.
> 
> Changes from V2:
> - Avoid introducing new states and spinlocks by reusuing the NAPI
>   state
> - Fix the budget calculation in virtnet_poll()
> - Drop patch 1/3 from V2 since it was useless
> 
> Changes from V1:
> - split the patch info smaller ones
> - add more details about test setup/configuration

Series applied, thanks Jason.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html