netdev - Re: sit tunnel slow since added GSO/TSO support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <52ACCCB3.7010401@redhat.com>
Date:	Sat, 14 Dec 2013 22:25:07 +0100
From:	Michal Schmidt <mschmidt@...hat.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Eric Dumazet <edumazet@...gle.com>
Subject: Re: sit tunnel slow since added GSO/TSO support

On 12/13/2013 11:54 PM, Eric Dumazet wrote:
> I tried the same setup than before and got good behavior on current
> net-next kernel
>
> modprobe sit
> ip link set sit0 up
> ip -6 addr add dev sit0 2002:af6:1153::/64
> ip -6 ro add 2002:a00::/24 via fe80:: dev sit0

Eric,
in my test I do not use sit0. I create a new tunnel interface:
ip tun add sittun mode sit remote $REMOTE_IPV4 local $LOCAL_IPV4 \
   dev $IFACE

Looking at "ip tun show" I see that sit0 has the nopmtudisc option by 
default, while sittun does not.

As I wrote in my original message, using nopmtudisc when creating my 
tunnel interface works around the problem.

So I think nopmtudisc is the key difference in our setups.

Regards,
Michal

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html