From: Eric Dumazet <eric.dumazet@gmail.com>
To: Mark Smith <lk-netdev@lk-netdev.nosense.org>
Cc: "Gustavo F. Padovan" <gustavo@padovan.org>,
netdev@vger.kernel.org, marco bonola <marco.bonola@gmail.com>,
"ZioPRoTo (Saverio Proto)" <zioproto@gmail.com>,
Behling Mario <mb@mariobehling.de>,
"L. Aaron Kaplan" <aaron@lo-res.org>
Subject: Re: IP/UDP encapsulation
Date: Thu, 08 Apr 2010 12:29:33 +0200 [thread overview]
Message-ID: <1270722573.2215.47.camel@edumazet-laptop> (raw)
In-Reply-To: <20100408191831.08cd8d7b@opy.nosense.org>
Le jeudi 08 avril 2010 à 19:18 +0930, Mark Smith a écrit :
> On Thu, 8 Apr 2010 04:42:47 -0300
> "Gustavo F. Padovan" <gustavo@padovan.org> wrote:
>
> > Hi,
> >
> > I'm looking for some advice on that work. The Freifunk organization is
> > planning work on the IP/UDP encapsulation kernel module as a GSoC
> > project. The idea is to create a IP-in-UDP tunnel like we do for
> > IP-in-IP or IP-in-GRE tunnels. The only way to do that today is to use
> > some VPN software.
> >
> > The module will export its virtual interface through sockets and will
> > have support for the standard syscalls like the others encapsulation
> > modules.
> >
> > It will improve the performance of mesh networks that will we be able
> > to use IP-in-UDP rather than IP-in-IP.
>
> I'm a bit confused. How can tunnelling IP in UDP in IP be faster than IP in IP?
>
Maybe the 'gateway' doesnt handle IPIP at all ;)
Until 2.6.32, IPIP tunnels were not so scalable then UDP (RCU enabled)
ipip_rcv() was hitting a global rwlock
git describe 8f95dd63a2ab6fe7243c4f0bd2c3266e3a5525ab
v2.6.32-rc3-468-g8f95dd6
next prev parent reply other threads:[~2010-04-08 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 7:42 IP/UDP encapsulation Gustavo F. Padovan
2010-04-08 7:58 ` Eric Dumazet
2010-04-08 9:48 ` Mark Smith
2010-04-08 10:29 ` Eric Dumazet [this message]
2010-04-08 10:39 ` ZioPRoTo (Saverio Proto)
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=1270722573.2215.47.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=aaron@lo-res.org \
--cc=gustavo@padovan.org \
--cc=lk-netdev@lk-netdev.nosense.org \
--cc=marco.bonola@gmail.com \
--cc=mb@mariobehling.de \
--cc=netdev@vger.kernel.org \
--cc=zioproto@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox