Open Stack

Hi Alberto,
May I know the flavor and image you were using to do this test. TSO seems
to be a method that moves the process of tcp segmentation off to the nic
card.

I believe in OpenStack the nic is a tap interface that kvm attaches your
instance to and hence you have offloaded the task of segmenting to the host
cpu now ( I am only guessing, not sure).

I would like to know if this is the case and using a better flavor and
image would offer you better results without tinkering with the interface.

Thank you,
Ageeleshwar K

On Mon, Nov 10, 2014 at 5:41 PM, Alberto Molina Coballes <
alb.molina at gmail.com> wrote:

> 2014-11-09 21:37 GMT+01:00 George Shuklin <george.shuklin at gmail.com>:
>
>> Try to disable GRO on interfaces. It's well known bug, causing
>> significant net performance drop in case of the GRE tunnels.
>>
>> (Use ethtool)
>>
> Hi George,
>
> Thanks for your reply, but as mentioned in first message disabling GRO in
> physical interfaces doesn't improve the performance (step 5), only
> disabling TSO in virtual interfaces causes a significant improvement. the
> problem with that is a modification is needed every time an instance is
> launched.
>
> Cheers
>
> Alberto
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20141110/66fd433e/attachment.html>