M
MrJacK
Guest
ok, strange tool, very buggy installation routine...
I'm agree with you
No crash ? Very strange, i can reproduce it each time.
Which kernel do you use for the test ?
ok, strange tool, very buggy installation routine...
Hi,I'm agree with you
No crash ? Very strange, i can reproduce it each time.
Which kernel do you use for the test ?
Hi Tom,I just did more test with my KVM guests, just to make sure that I got the same setup.
I have two servers (IMS blades), running 2.6.32 (pvetest with kvm 0.14), KVM virtio network. On the second blade I run a KVM guest, e.g. Ubuntu 10.10. now, I am doing iperf tests from this guest to the first blade.
results in both directions: 940 Mbits/sec (I have only Gbit LAN in my IMS so its just perfect)
so where is the difference in our tests?
I had ran some test using RHEL6 KVM host, and NOT observed any performance issue with or without VLAN.
But I am able to replicate the issue in-house with virtual environment PROXMOX (you have provided).
I had a discussion with the Engineering Team about this behaviour and it seems, the issue is related to the kernel. Kernel does not seems to be working fine with TCP Segmentation Offload "tso" ON with vlan and bridge interface configured.
And to confirm this I ran some test on PROXMOX VE with "tso off" and observed a fine performance even with VLAN( 802.1q).
So as a workaround we recommend you to turn off the "tso" on the host interface.
Please use following command to turn off the tso:
# ethtool -K <interface> tso off
Is it possible to enable this inside the kernel? Or why is there a difference to the RHEL-Kernel?
Hi Dietmar,What driver do we talk about (exactly)?
modinfo sfc
filename: /lib/modules/2.6.35-1-pve/kernel/drivers/net/sfc/sfc.ko
license: GPL
description: Solarflare Communications network driver
author: Solarflare Communications and Michael Brown <mbrown@fensystems.co.uk>
srcversion: B4831765C939D27E214D619
alias: pci:v00001924d00000813sv*sd*bc*sc*i*
alias: pci:v00001924d00000803sv*sd*bc*sc*i*
alias: pci:v00001924d00000710sv*sd*bc*sc*i*
alias: pci:v00001924d00000703sv*sd*bc*sc*i*
depends: mtd,mdio,i2c-algo-bit
vermagic: 2.6.35-1-pve SMP mod_unload modversions
parm: rx_alloc_method:Allocation method used for RX buffers (int)
parm: rx_refill_threshold:RX descriptor ring fast/slow fill threshold (%) (uint)
parm: rx_xoff_thresh_bytes:RX fifo XOFF threshold (int)
parm: rx_xon_thresh_bytes:RX fifo XON threshold (int)
parm: separate_tx_channels:Use separate channels for TX and RX (uint)
parm: rss_cpus:Number of CPUs to use for Receive-Side Scaling (uint)
parm: phy_flash_cfg:Set PHYs into reflash mode initially (int)
parm: irq_adapt_low_thresh:Threshold score for reducing IRQ moderation (uint)
parm: irq_adapt_high_thresh:Threshold score for increasing IRQ moderation (uint)
parm: interrupt_mode:Interrupt mode (0=>MSIX 1=>MSI 2=>legacy) (uint)
there a a much newer driver, but with the same behavior
Hi Dietmar,I can't see any option to disable that at compile time.
Hi Dietmar,
right - the problem is with the kernel. I don't know where - i know only the workaround with tso-off.
Perhaps you know which kernel-changes (related to RHEL-Kernel) can make a different behavior in relation to tso??
Hi,I guess the problem is inside the Solaflare driver, so that question should go to Solaflare support?