[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54C138BB.7000407@6wind.com>
Date: Thu, 22 Jan 2015 18:51:55 +0100
From: Vincent JARDIN <vincent.jardin@...nd.com>
To: Tom Herbert <therbert@...gle.com>
CC: Jesse Gross <jesse@...ira.com>, Pravin Shelar <pshelar@...ira.com>,
David Miller <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next 0/3] openvswitch: Add STT support.
On 22/01/2015 17:24, Tom Herbert wrote:
> STT is undoubtedly a creative and unique solution I'll give you that,
> but the potential repercussions of allowing this to be widely deployed
> are profound. IMO this needs to be fully explored before it can ever
> be allowed in the kernel. If there has already been discussion on this
> please forward a pointer (I didn't find anything in the IETF mailing
> list archives other than the draft posting announcements), but at the
> minimum these patches warrant a lot of scrutiny.
I share this concern of biased use of TCP, all the critics will be
valid. But anyone can hack TCP (so peer to peer software does or CDN
software does). So, I prefer the let the freedom to the sysadmin to
enable/disable it for their networks. Not having this feature into the
kernel prevent sysadmin from doing it. To be safe, it can be an
experimental feature of the Linux kernel.
Same: LRO/GRO is is bad features: it breaks many times networking (most
IP forwarders must disable it), but it helps for servers. Same for STT
in fact, it has its narrow set of use-cases which are valid.
Best regards,
Vincent
--
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
Powered by blists - more mailing lists