netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: David Miller <davem@davemloft.net>
Cc: tom@herbertland.com, netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH net-next 0/8] tou: Transports over UDP - part I
Date: Thu, 23 Jun 2016 09:50:50 +0200	[thread overview]
Message-ID: <576B94DA.7070804@nod.at> (raw)
In-Reply-To: <20160623.034004.1518087003165708123.davem@davemloft.net>

Am 23.06.2016 um 09:40 schrieb David Miller:
> From: Richard Weinberger <richard.weinberger@gmail.com>
> Date: Thu, 23 Jun 2016 00:15:04 +0200
> 
>> On Thu, Jun 16, 2016 at 7:51 PM, Tom Herbert <tom@herbertland.com> wrote:
>>> Transports over UDP is intended to encapsulate TCP and other transport
>>> protocols directly and securely in UDP.
>>>
>>> The goal of this work is twofold:
>>>
>>> 1) Allow applications to run their own transport layer stack (i.e.from
>>>    userspace). This eliminates dependencies on the OS (e.g. solves a
>>>    major dependency issue for Facebook on clients).
>>
>> Facebook on clients would be a Facebook app on mobile devices?
>> Does that mean that the Facebook app is so advanced and complicated
>> that it needs a special TCP stack?!
> 
> No, the TCP stack in the android/iOS/Windows kernel is so out of date
> that in order to get even moderately recent TCP features it is
> necessary to do this.

I see.
So the plan is bringing TOU into almost every kernel out there
and then ship Apps with their own TCP stacks since vendors are unable
to deliver decent updates.

I didn't realize that the situation is *that* worse. :(

Thanks,
//richard

  reply	other threads:[~2016-06-23  7:50 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16 17:51 [PATCH net-next 0/8] tou: Transports over UDP - part I Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 1/8] net: Change SKB_GSO_DODGY to be a tx_flag Tom Herbert
2016-06-16 18:58   ` Alexander Duyck
2016-06-16 20:18     ` Tom Herbert
2016-06-16 20:33       ` Alexander Duyck
2016-06-17 22:33     ` Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 2/8] fou: Change ip_tunnel_encap to take net argument Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 3/8] tou: Base infrastructure for Transport over UDP Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 4/8] ipv4: Support TOU Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 5/8] tcp: Support for TOU Tom Herbert
2016-06-16 17:52 ` [PATCH net-next 6/8] ipv6: Support TOU Tom Herbert
2016-06-16 17:52 ` [PATCH net-next 7/8] tcp6: Support for TOU Tom Herbert
2016-06-16 17:52 ` [PATCH net-next 8/8] tou: Support for GSO Tom Herbert
2016-06-16 18:10 ` [PATCH net-next 0/8] tou: Transports over UDP - part I Rick Jones
2016-06-16 23:15 ` Hannes Frederic Sowa
2016-06-17 16:51   ` Tom Herbert
2016-06-21 16:56     ` Hannes Frederic Sowa
2016-06-18  3:09 ` David Miller
2016-06-18  3:52   ` Tom Herbert
2016-06-19 20:15     ` Hajime Tazaki
2016-06-20  3:07     ` David Miller
2016-06-20 15:13       ` Tom Herbert
2016-06-21  8:29         ` David Miller
2016-06-22  3:42           ` Jerry Chu
2016-06-22  4:06             ` David Ahern
2016-06-22 19:24               ` David Miller
2016-06-22 17:40             ` Tom Herbert
2016-06-22 19:23             ` David Miller
2016-06-25 15:56               ` Tom Herbert
2016-06-21 17:11     ` Hannes Frederic Sowa
2016-06-21 17:23       ` Tom Herbert
2016-06-22 22:15 ` Richard Weinberger
2016-06-22 22:56   ` Tom Herbert
2016-06-23  7:40   ` David Miller
2016-06-23  7:50     ` Richard Weinberger [this message]
2016-06-24 21:12       ` Tom Herbert
2016-06-24 21:36         ` Rick Jones
2016-06-24 21:46           ` Tom Herbert
2016-06-24 22:06             ` Rick Jones
2016-06-24 23:43               ` Tom Herbert
2016-06-25  0:01                 ` Rick Jones
2016-06-25 16:22                   ` Tom Herbert

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=576B94DA.7070804@nod.at \
    --to=richard@nod.at \
    --cc=davem@davemloft.net \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=tom@herbertland.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;
as well as URLs for NNTP newsgroup(s).