search for: ioexits

...polling was specified ioctl. >> >> Test were done through: >> >> - 50 us as busy loop timeout >> - Netperf 2.6 >> - Two machines with back to back connected ixgbe >> - Guest with 1 vcpu and 1 queue >> >> Results: >> - For stream workload, ioexits were reduced dramatically in medium >> size (1024-2048) of tx (at most -39%) and almost all rx (at most >> -79%) as a result of polling. This compensate for the possible >> wasted cpu cycles more or less. That porbably why we can still see >> some increasing in the n...

...polling was specified ioctl. >> >> Test were done through: >> >> - 50 us as busy loop timeout >> - Netperf 2.6 >> - Two machines with back to back connected ixgbe >> - Guest with 1 vcpu and 1 queue >> >> Results: >> - For stream workload, ioexits were reduced dramatically in medium >> size (1024-2048) of tx (at most -39%) and almost all rx (at most >> -79%) as a result of polling. This compensate for the possible >> wasted cpu cycles more or less. That porbably why we can still see >> some increasing in the n...

...x receive socket for a while. The maximum number of time (in us) could be spent on busy polling was specified ioctl. Test were done through: - 50 us as busy loop timeout - Netperf 2.6 - Two machines with back to back connected ixgbe - Guest with 1 vcpu and 1 queue Results: - For stream workload, ioexits were reduced dramatically in medium size (1024-2048) of tx (at most -39%) and almost all rx (at most -79%) as a result of polling. This compensate for the possible wasted cpu cycles more or less. That porbably why we can still see some increasing in the normalized throughput in some cases....

...x receive socket for a while. The maximum number of time (in us) could be spent on busy polling was specified ioctl. Test were done through: - 50 us as busy loop timeout - Netperf 2.6 - Two machines with back to back connected ixgbe - Guest with 1 vcpu and 1 queue Results: - For stream workload, ioexits were reduced dramatically in medium size (1024-2048) of tx (at most -39%) and almost all rx (at most -79%) as a result of polling. This compensate for the possible wasted cpu cycles more or less. That porbably why we can still see some increasing in the normalized throughput in some cases....

...> time (in us) could be spent on busy polling was specified ioctl. > > Test were done through: > > - 50 us as busy loop timeout > - Netperf 2.6 > - Two machines with back to back connected ixgbe > - Guest with 1 vcpu and 1 queue > > Results: > - For stream workload, ioexits were reduced dramatically in medium > size (1024-2048) of tx (at most -39%) and almost all rx (at most > -79%) as a result of polling. This compensate for the possible > wasted cpu cycles more or less. That porbably why we can still see > some increasing in the normalized throug...

...r latency (TCP_RR). - Get a better or minor regression on most of the TX tests, but see some regression on 4096 size. - Except for 8 sessions of 4096 size RX, have a better or same performance. - CPU utilization were incrased as expected. TCP_RR: size/session/+thu%/+normalize%/+tpkts%/+rpkts%/+ioexits%/ 1/ 1/ +8%/ -32%/ +8%/ +8%/ +7% 1/ 50/ +7%/ -19%/ +7%/ +7%/ +1% 1/ 100/ +5%/ -21%/ +5%/ +5%/ 0% 1/ 200/ +5%/ -21%/ +7%/ +7%/ +1% 64/ 1/ +11%/ -29%/ +11%/ +11%/ +10% 64/ 50/ +7%/ -19%/ +8%/ +8%/ +2% 64/...

...r latency (TCP_RR). - Get a better or minor regression on most of the TX tests, but see some regression on 4096 size. - Except for 8 sessions of 4096 size RX, have a better or same performance. - CPU utilization were incrased as expected. TCP_RR: size/session/+thu%/+normalize%/+tpkts%/+rpkts%/+ioexits%/ 1/ 1/ +8%/ -32%/ +8%/ +8%/ +7% 1/ 50/ +7%/ -19%/ +7%/ +7%/ +1% 1/ 100/ +5%/ -21%/ +5%/ +5%/ 0% 1/ 200/ +5%/ -21%/ +7%/ +7%/ +1% 64/ 1/ +11%/ -29%/ +11%/ +11%/ +10% 64/ 50/ +7%/ -19%/ +8%/ +8%/ +2% 64/...

...t; >>> Test were done through: >>> >>> - 50 us as busy loop timeout >>> - Netperf 2.6 >>> - Two machines with back to back connected ixgbe >>> - Guest with 1 vcpu and 1 queue >>> >>> Results: >>> - For stream workload, ioexits were reduced dramatically in medium >>> size (1024-2048) of tx (at most -39%) and almost all rx (at most >>> -79%) as a result of polling. This compensate for the possible >>> wasted cpu cycles more or less. That porbably why we can still see >>> some inc...

...or minor regression on most of the TX tests, but see > some regression on 4096 size. > - Except for 8 sessions of 4096 size RX, have a better or same > performance. > - CPU utilization were incrased as expected. > > TCP_RR: > size/session/+thu%/+normalize%/+tpkts%/+rpkts%/+ioexits%/ > 1/ 1/ +8%/ -32%/ +8%/ +8%/ +7% > 1/ 50/ +7%/ -19%/ +7%/ +7%/ +1% > 1/ 100/ +5%/ -21%/ +5%/ +5%/ 0% > 1/ 200/ +5%/ -21%/ +7%/ +7%/ +1% > 64/ 1/ +11%/ -29%/ +11%/ +11%/ +10% > 64/ 50/ +7%/ -19%/...

...receive socket for a while. The maximum number of time (in us) could be spent on busy polling was specified ioctl. Test A were done through: - 50 us as busy loop timeout - Netperf 2.6 - Two machines with back to back connected ixgbe - Guest with 1 vcpu and 1 queue Results: - For stream workload, ioexits were reduced dramatically in medium size (1024-2048) of tx (at most -43%) and almost all rx (at most -84%) as a result of polling. This compensate for the possible wasted cpu cycles more or less. That porbably why we can still see some increasing in the normalized throughput in some cases. - Throug...

...receive socket for a while. The maximum number of time (in us) could be spent on busy polling was specified ioctl. Test A were done through: - 50 us as busy loop timeout - Netperf 2.6 - Two machines with back to back connected ixgbe - Guest with 1 vcpu and 1 queue Results: - For stream workload, ioexits were reduced dramatically in medium size (1024-2048) of tx (at most -43%) and almost all rx (at most -84%) as a result of polling. This compensate for the possible wasted cpu cycles more or less. That porbably why we can still see some increasing in the normalized throughput in some cases. - Throug...

...cted mlx4 - Guest with 8 vcpus and 1 queue Results: - TCP_RR was imporved obviously (at most 27%). And cpu utilizaton was also improved in this case. - No obvious differences in Guest RX throughput. - Guest TX throughput was also improved. TCP_RR: size/session/+thu%/+normalize%/+tpkts%/+rpkts%/+ioexits%/ 1/ 1/ +27%/ 0%/ +27%/ +27%/ +25% 1/ 50/ +2%/ +1%/ +2%/ +2%/ -4% 1/ 100/ +2%/ +1%/ +3%/ +3%/ -14% 1/ 200/ +2%/ +2%/ +5%/ +5%/ -15% 64/ 1/ +20%/ -13%/ +20%/ +20%/ +20% 64/ 50/ +17%/ +14%/ +16%/ +16%/ -11% 64/...

...cted mlx4 - Guest with 8 vcpus and 1 queue Results: - TCP_RR was imporved obviously (at most 27%). And cpu utilizaton was also improved in this case. - No obvious differences in Guest RX throughput. - Guest TX throughput was also improved. TCP_RR: size/session/+thu%/+normalize%/+tpkts%/+rpkts%/+ioexits%/ 1/ 1/ +27%/ 0%/ +27%/ +27%/ +25% 1/ 50/ +2%/ +1%/ +2%/ +2%/ -4% 1/ 100/ +2%/ +1%/ +3%/ +3%/ -14% 1/ 200/ +2%/ +2%/ +5%/ +5%/ -15% 64/ 1/ +20%/ -13%/ +20%/ +20%/ +20% 64/ 50/ +17%/ +14%/ +16%/ +16%/ -11% 64/...