`<div class="gmail_quote">Thanks Theo, I will see what I can pull. I think grabbing just the aggr module is the best option at the moment.<br><br>The guest is Gentoo (Kernel 3.2.12).<br><br>Here's the performance bottleneck I'm seeing ..<br>
<br>gazoo is OmniOS host with 2 x igb in L4 aggr with main lan on VLAN 300<br>slate is Gentoo KVM on OmniOS with 1 x virtio vnic on aggr VLAN 300<br>myth is Gentoo phys with 1 x nvidia single gige with main lan on VLAN 300<br>
<br>Issue:<br>gazoo <> myth = good<br>anything <> slate = bad<br><br>Examples:<br><br>myth ~ # iperf -c gazoo<br>------------------------------------------------------------<br>Client connecting to gazoo, TCP port 5001<br>
TCP window size: 22.5 KByte (default)<br>------------------------------------------------------------<br>[ 3] local 192.168.245.136 port 60917 connected with 192.168.245.134 port 5001<br>[ ID] Interval Transfer Bandwidth<br>
[ 3] 0.0-10.0 sec 1.09 GBytes 932 Mbits/sec<br><br>root@gazoo ~ # iperf -c myth<br>------------------------------------------------------------<br>Client connecting to myth, TCP port 5001<br>TCP window size: 48.0 KByte (default)<br>
------------------------------------------------------------<br>[ 4] local 192.168.245.134 port 36001 connected with 192.168.245.136 port 5001<br>[ ID] Interval Transfer Bandwidth<br>[ 4] 0.0-10.0 sec 1.05 GBytes 899 Mbits/sec<br>
<br>root@gazoo ~ # iperf -c slate<br>------------------------------------------------------------<br>Client connecting to slate, TCP port 5001<br>TCP window size: 48.0 KByte (default)<br>------------------------------------------------------------<br>
[ 4] local 192.168.245.134 port 51500 connected with 192.168.245.152 port 5001<br>[ ID] Interval Transfer Bandwidth<br><b>[ 4] 0.0-10.0 sec 26.5 MBytes 22.2 Mbits/sec</b><br><br><br>myth ~ # iperf -c slate<br>
------------------------------------------------------------<br>Client connecting to slate, TCP port 5001<br>TCP window size: 22.5 KByte (default)<br>------------------------------------------------------------<br>[ 3] local 192.168.245.136 port 56461 connected with 192.168.245.152 port 5001<br>
[ ID] Interval Transfer Bandwidth<br><b>[ 3] 0.0-10.2 sec 91.8 MBytes 75.3 Mbits/sec</b><div class="HOEnZb"><div class="h5"><br><br><br><div class="gmail_quote">On Mon, Jul 9, 2012 at 10:53 AM, Theo Schlossnagle <span dir="ltr"><<a href="mailto:jesus@omniti.com" target="_blank">jesus@omniti.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yes. If you switch to the bloody repo, you should be able to do a pkg<br>
update and get a new kernel.<br>
<br>
The release publisher is: <a href="http://pkg.omniti.com/omnios/release/" target="_blank">http://pkg.omniti.com/omnios/release/</a><br>
Bloody's publisher is: <a href="http://pkg.omniti.com/omnios/bloody/" target="_blank">http://pkg.omniti.com/omnios/bloody/</a><br>
<br>
pkg unset-publisher omnios<br>
pkg set-publisher -g <a href="http://pkg.omniti.com/omnios/bloody/" target="_blank">http://pkg.omniti.com/omnios/bloody/</a> omnios<br>
pkg update<br>
<br>
This should give you a new BE running bloody to reboot into.<br>
<br>
Alternatively, you could just snag the aggr module from bloody and<br>
replace the one you have.<br>
<br>
There are a couple of severe performance pathologies regarding<br>
networking under qemu/kvm, can you say what the guest is?<br>
<div><div><br>
On Sun, Jul 8, 2012 at 8:24 PM, Denis Cheong <<a href="mailto:denis@denisandyuki.net" target="_blank">denis@denisandyuki.net</a>> wrote:<br>
> Hi Theo<br>
><br>
> Is there an easy way that I can test your proposed fix to this issue?<br>
><br>
> I am having major network performance bottlenecks in KVM and I suspect that<br>
> it has something to do with the duplicate packets, so would like to test it<br>
> out.<br>
<br>
<br>
</div></div><span><font color="#888888">--<br>
Theo Schlossnagle<br>
<br>
<a href="http://omniti.com/is/theo-schlossnagle" target="_blank">http://omniti.com/is/theo-schlossnagle</a><br>
</font></span></blockquote></div><br>
</div></div></div><br>
`