diff options
author | 2012-01-12 15:44:42 +1030 | |
---|---|---|
committer | 2012-01-12 15:44:42 +1030 | |
commit | 7b21e34fd1c272e3a8c3846168f2f6287a4cd72b (patch) | |
tree | 0f94c9f834f5b7cd8ba87168df892ed17b09cb8f /crypto/api.c | |
parent | Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost (diff) | |
download | wireguard-linux-7b21e34fd1c272e3a8c3846168f2f6287a4cd72b.tar.xz wireguard-linux-7b21e34fd1c272e3a8c3846168f2f6287a4cd72b.zip |
virtio: harsher barriers for rpmsg.
We were cheating with our barriers; using the smp ones rather than the
real device ones. That was fine, until rpmsg came along, which is
used to talk to a real device (a non-SMP CPU).
Unfortunately, just putting back the real barriers (reverting
d57ed95d) causes a performance regression on virtio-pci. In
particular, Amos reports netbench's TCP_RR over virtio_net CPU
utilization increased up to 35% while throughput went down by up to
14%.
By comparison, this branch is in the noise.
Reference: https://lkml.org/lkml/2011/12/11/22
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Diffstat (limited to 'crypto/api.c')
0 files changed, 0 insertions, 0 deletions