search for: throughput_mbp

Displaying 5 results from an estimated 5 matches for "throughput_mbp".

Did you mean: throughput_mbps
2017 Apr 07
2
[PATCH net-next 3/3] virtio-net: clean tx descriptors from rx napi
...affinity (rx,tx). Process is always pinned to cpu 1. This is a 4 vcpu system pinned by the host to 4 cores on the same socket. The previously reported results were obtained with txq, rtx and process on different vcpus (0,2). Running all on the same vcpu lower cycle count considerably: irq 0,0 1 throughput_Mbps=29767.14 391,488,924,526 cycles 10 throughput_Mbps=40808.64 424,530,251,896 cycles 100 throughput_Mbps=33475.13 414,622,071,167 cycles irq 0,2 1 throughput_Mbps=30176.05 395,673,200,747 cycles 10 throughput_Mbps=40729.26 433,948,374,991 cycles 100 throughput_Mbps=...
2017 Apr 07
2
[PATCH net-next 3/3] virtio-net: clean tx descriptors from rx napi
...affinity (rx,tx). Process is always pinned to cpu 1. This is a 4 vcpu system pinned by the host to 4 cores on the same socket. The previously reported results were obtained with txq, rtx and process on different vcpus (0,2). Running all on the same vcpu lower cycle count considerably: irq 0,0 1 throughput_Mbps=29767.14 391,488,924,526 cycles 10 throughput_Mbps=40808.64 424,530,251,896 cycles 100 throughput_Mbps=33475.13 414,622,071,167 cycles irq 0,2 1 throughput_Mbps=30176.05 395,673,200,747 cycles 10 throughput_Mbps=40729.26 433,948,374,991 cycles 100 throughput_Mbps=...
2017 Apr 07
0
[PATCH net-next 3/3] virtio-net: clean tx descriptors from rx napi
...pinned to cpu > 1. This is a 4 vcpu system pinned by the host to 4 cores on the same > socket. The previously reported results were obtained with txq, rtx > and process on different vcpus (0,2). Running all on the same vcpu > lower cycle count considerably: > > irq 0,0 > 1 throughput_Mbps=29767.14 391,488,924,526 cycles > 10 throughput_Mbps=40808.64 424,530,251,896 cycles > 100 throughput_Mbps=33475.13 414,622,071,167 cycles > > irq 0,2 > 1 throughput_Mbps=30176.05 395,673,200,747 cycles > 10 throughput_Mbps=40729.26 433,948,374,991...
2017 Apr 03
2
[PATCH net-next 3/3] virtio-net: clean tx descriptors from rx napi
On Sun, Apr 2, 2017 at 10:47 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Sun, Apr 02, 2017 at 04:10:12PM -0400, Willem de Bruijn wrote: >> From: Willem de Bruijn <willemb at google.com> >> >> Amortize the cost of virtual interrupts by doing both rx and tx work >> on reception of a receive interrupt if tx napi is enabled. With >>
2017 Apr 03
2
[PATCH net-next 3/3] virtio-net: clean tx descriptors from rx napi
On Sun, Apr 2, 2017 at 10:47 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Sun, Apr 02, 2017 at 04:10:12PM -0400, Willem de Bruijn wrote: >> From: Willem de Bruijn <willemb at google.com> >> >> Amortize the cost of virtual interrupts by doing both rx and tx work >> on reception of a receive interrupt if tx napi is enabled. With >>