| commit | 36ad0f356d159f9a99f74f2fd4559443ef9af7f9 | |
| author | Imre Vadász <imre@vdsz.com> | |
| Sun, 25 Mar 2018 19:59:43 +0000 (25 21:59 +0200) | ||
| committer | Imre Vadász <imre@vdsz.com> | |
| Sun, 25 Mar 2018 20:04:17 +0000 (25 22:04 +0200) | ||
| tree | 5f294de454a13f7dda0892d22a10e14e07df35a3 | treesnapshot (tar.gz zip) |
| parent | af62becb69fced07907e16f75095de297a34eaba | commitdiff |
if_vtnet - Don't drop vtnet_slz in some of the virtqueue_notify() calls.
* There are several cases where the vtnet_slz serializer is dropped around
virtqueue_notify() calls, with the hope that this allows other cores to
run if_vtnet code in parallel.
* In vtnet_exec_ctrl_cmd(), it shouldn't make a significant performance
difference, and avoids some theoretical race possibilities.
* In the vtnet_init_rx_vq initialization code, it also is irrelevant for
performance, and only complicates things.
* In the vtnet_rxeof() and vtnet_start() cases it might actually be relevant
for performance, so we keep those for now. When changing the driver to
use the MULTI_SERIALIZERS MODE, the serializer dropping can also be
removed in those two cases.
* There are several cases where the vtnet_slz serializer is dropped around
virtqueue_notify() calls, with the hope that this allows other cores to
run if_vtnet code in parallel.
* In vtnet_exec_ctrl_cmd(), it shouldn't make a significant performance
difference, and avoids some theoretical race possibilities.
* In the vtnet_init_rx_vq initialization code, it also is irrelevant for
performance, and only complicates things.
* In the vtnet_rxeof() and vtnet_start() cases it might actually be relevant
for performance, so we keep those for now. When changing the driver to
use the MULTI_SERIALIZERS MODE, the serializer dropping can also be
removed in those two cases.
| sys/dev/virtual/virtio/net/if_vtnet.c | diffblobblamehistory |