search for: incrased

Displaying 4 results from an estimated 4 matches for "incrased".

Did you mean: increased
2016 Mar 04
6
[PATCH V4 0/3] basic busy polling support for vhost_net
...- Guest with 1 vcpus and 1 queue Results: - Obvious improvements (%5 - 20%) for 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%/...
2016 Mar 04
6
[PATCH V4 0/3] basic busy polling support for vhost_net
...- Guest with 1 vcpus and 1 queue Results: - Obvious improvements (%5 - 20%) for 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%/...
2016 Mar 09
0
[PATCH V4 0/3] basic busy polling support for vhost_net
...gt; Results: > - Obvious improvements (%5 - 20%) for 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%...
2008 Jun 18
4
[LLVMdev] LLVM on OpenBSD
Holger Schurig wrote: >> With 3.3.5 my first test took 5 times to produce a non "bus >> error" build. There were no 'make cleans' in between. >> >> What is going on? > > You mean you used your bsd-ports-provided gcc to compile LLVM and > you've got 4 times a bus-error during the build? In this case, > it cannot be a LLVM problem. Ok,