From: Michal Schmidt <mschmidt@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: sit tunnel slow since added GSO/TSO support
Date: Sat, 14 Dec 2013 22:25:07 +0100 [thread overview]
Message-ID: <52ACCCB3.7010401@redhat.com> (raw)
In-Reply-To: <1386975268.19078.190.camel@edumazet-glaptop2.roam.corp.google.com>
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
next prev parent reply other threads:[~2013-12-14 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 16:13 sit tunnel slow since added GSO/TSO support Michal Schmidt
2013-12-13 16:28 ` Eric Dumazet
2013-12-13 22:54 ` Eric Dumazet
2013-12-14 21:25 ` Michal Schmidt [this message]
2013-12-15 1:23 ` Eric Dumazet
2013-12-16 14:31 ` [PATCH] ipv6: sit: update mtu check to take care of gso packets Eric Dumazet
2013-12-17 14:22 ` Michal Schmidt
2013-12-17 14:48 ` Eric Dumazet
2013-12-17 20:19 ` Hannes Frederic Sowa
2013-12-17 21:34 ` Eric Dumazet
2013-12-18 22:57 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52ACCCB3.7010401@redhat.com \
--to=mschmidt@redhat.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.