From: David Miller <davem@davemloft.net>
To: pshelar@nicira.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/6] net: Add STT support.
Date: Sat, 31 Jan 2015 17:40:37 -0800 (PST) [thread overview]
Message-ID: <20150131.174037.1176748996497876060.davem@davemloft.net> (raw)
In-Reply-To: <1422574156-1831-1-git-send-email-pshelar@nicira.com>
From: Pravin B Shelar <pshelar@nicira.com>
Date: Thu, 29 Jan 2015 15:29:16 -0800
> Following patch series adds support for Stateless Transport
> Tunneling protocol.
> STT uses TCP segmentation offload available in most of NIC. On
> packet xmit STT driver appends STT header along with TCP header
> to the packet. For GSO packet GSO parameters are set according
> to tunnel configuration and packet is handed over to networking
> stack. This allows use of segmentation offload available in NICs
I don't like this at all.
Routers _absolutely_ depend upon the ability to make TCP flows back
off by dropping packets in various ways (tail drop, RED random drops,
etc.). STT violates this completely.
It's _NOT_ TCP, you can't put lipstick on a pig and pretend it's not a
pig. You need to use something that indicates it's flow properties,
a datagram protocol. Either via an existing one or by creating a new
one.
I know you want to do this mass TCP behavioral violation because of
TSO. But that's too bad. The ends do not justify the means.
I also don't buy the argument that "people can put arbitrary changes
into their kernel to do stuff like that".
They can't do it to the stack I'm willing to maintain, and that's what
matters for %99 of systems out there.
next prev parent reply other threads:[~2015-02-01 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 23:29 [PATCH net-next v2 0/6] net: Add STT support Pravin B Shelar
2015-01-30 3:46 ` Alexander Duyck
2015-01-30 4:04 ` Pravin Shelar
2015-01-30 4:17 ` Tom Herbert
2015-01-30 5:03 ` Pravin Shelar
2015-01-30 18:44 ` Andy Gospodarek
2015-02-02 18:44 ` Pravin Shelar
2015-01-30 16:46 ` Rick Jones
2015-02-01 1:40 ` David Miller [this message]
2015-02-02 18:44 ` Pravin Shelar
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=20150131.174037.1176748996497876060.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.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).