From: Vincent JARDIN <vincent.jardin@6wind.com>
To: Tom Herbert <therbert@google.com>
Cc: Jesse Gross <jesse@nicira.com>,
Pravin Shelar <pshelar@nicira.com>,
David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/3] openvswitch: Add STT support.
Date: Thu, 22 Jan 2015 18:51:55 +0100 [thread overview]
Message-ID: <54C138BB.7000407@6wind.com> (raw)
In-Reply-To: <CA+mtBx9pnkJBVftqFTK6fcd-toAxsJrvB=drTxWQs_=5s9C0+A@mail.gmail.com>
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
next prev parent reply other threads:[~2015-01-22 17:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 20:25 [PATCH net-next 0/3] openvswitch: Add STT support Pravin B Shelar
2015-01-20 23:06 ` Tom Herbert
2015-01-21 9:08 ` Pravin Shelar
2015-01-21 16:51 ` Tom Herbert
2015-01-21 18:30 ` Pravin Shelar
2015-01-21 19:45 ` Tom Herbert
2015-01-21 20:22 ` Eric Dumazet
2015-01-21 20:35 ` Jesse Gross
2015-01-21 21:54 ` Tom Herbert
2015-01-21 22:14 ` Jesse Gross
2015-01-21 23:46 ` Vincent JARDIN
2015-01-22 16:24 ` Tom Herbert
2015-01-22 17:51 ` Vincent JARDIN [this message]
2015-01-23 9:04 ` David Miller
2015-01-23 9:00 ` David Miller
2015-02-02 16:23 ` Tom Herbert
2015-02-02 20:39 ` Jesse Gross
2015-02-02 22:49 ` Tom Herbert
2015-01-23 16:58 ` Tom Herbert
2015-01-23 17:38 ` Jesse Gross
2015-01-23 18:25 ` Tom Herbert
2015-01-23 20:20 ` Jesse Gross
2015-01-23 20:57 ` Tom Herbert
2015-01-23 21:11 ` Pravin Shelar
2015-02-02 16:15 ` 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=54C138BB.7000407@6wind.com \
--to=vincent.jardin@6wind.com \
--cc=davem@davemloft.net \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=therbert@google.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 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.