From: Eric Dumazet <eric.dumazet@gmail.com>
To: Gilad Ben-Yossef <gilad@codefidence.com>
Cc: netdev@vger.kernel.org, ori@comsleep.com
Subject: Re: [PATCHv4 0/7] Per route TCP options support kill switches
Date: Wed, 28 Oct 2009 15:22:29 +0100 [thread overview]
Message-ID: <4AE853A5.3060804@gmail.com> (raw)
In-Reply-To: <1256739327-11576-1-git-send-email-gilad@codefidence.com>
Gilad Ben-Yossef a écrit :
> Allow selectively turning off support for specific TCP options
> on a per route basis.
>
> One normally want to disable SACK, DSACK, time stamp or window
> scale if one got a piece of broken networking equipment somewhere
> as a stop gap until you can bring a big enough hammer to deal with
> the broken network equipment. It doesn't make sense to "punish" the
> entire connections going through the machine to destinations not
> related to the broken equipment.
>
> This is doubly true when one is dealing with network containers
> used to isolate several virtual domains.
>
> Per route options implemented in free bits in the features route
> entry property, which in some cases were reserved by name for these
> options, so this does not inflate any structure.
>
> Global sysctls for these options are still preserved and retain
> the exact original meaning (e.g. you have to have both the global
> sysctl turned on and not turn off the TCP option parsing in the
> specific route to have it proccessed).
>
> It is not possible to turn off globally an option but turn it on
> per route, so as to not subtly change the meaning of current
> establish sysctls (and this is a rare need anyway).
>
> Tested on x86 using Qemu/KVM.
>
> Working but crude matching patch to iproute2 sent earlier to the list.
>
> Patchset based on original work by Ori Finkelman and Yony Amit
> from ComSleep Ltd.
>
> The author wishes to thank Eric Dumazaet, William Allen Simpson,
> Bill Fink and Ilpo Jarvinen for their feedback.
>
>
> Gilad Ben-Yossef (7):
> Only parse time stamp TCP option in time wait sock
> Allow tcp_parse_options to consult dst entry
> Add dst_feature to query route entry features
> Add the no SACK route option feature
> Allow disabling TCP timestamp options per route
> Allow to turn off TCP window scale opt per route
> Allow disabling of DSACK TCP option per route
>
> include/linux/rtnetlink.h | 6 ++++--
> include/net/dst.h | 8 +++++++-
> include/net/tcp.h | 3 ++-
> net/ipv4/syncookies.c | 27 ++++++++++++++-------------
> net/ipv4/tcp_input.c | 26 ++++++++++++++++++--------
> net/ipv4/tcp_ipv4.c | 21 ++++++++++++---------
> net/ipv4/tcp_minisocks.c | 9 ++++++---
> net/ipv4/tcp_output.c | 18 +++++++++++++-----
> net/ipv6/syncookies.c | 28 +++++++++++++++-------------
> net/ipv6/tcp_ipv6.c | 3 ++-
> 10 files changed, 93 insertions(+), 56 deletions(-)
>
I am a bit lost. What exactly changed in this new version, versus v3 ?
next prev parent reply other threads:[~2009-10-28 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 14:15 [PATCHv4 0/7] Per route TCP options support kill switches Gilad Ben-Yossef
2009-10-28 14:15 ` [PATCHv4 1/7] Only parse time stamp TCP option in time wait sock Gilad Ben-Yossef
2009-10-28 14:15 ` [PATCHv4 2/7] Allow tcp_parse_options to consult dst entry Gilad Ben-Yossef
2009-10-28 14:15 ` [PATCHv4 3/7] Add dst_feature to query route entry features Gilad Ben-Yossef
2009-10-28 14:15 ` [PATCHv4 4/7] Add the no SACK route option feature Gilad Ben-Yossef
2009-10-28 14:15 ` [PATCHv4 5/7] Allow disabling TCP timestamp options per route Gilad Ben-Yossef
2009-10-28 14:15 ` [PATCHv4 6/7] Allow to turn off TCP window scale opt " Gilad Ben-Yossef
2009-10-28 14:15 ` [PATCHv4 7/7] Allow disabling of DSACK TCP option " Gilad Ben-Yossef
2009-10-28 14:22 ` Eric Dumazet [this message]
2009-10-28 14:31 ` [PATCHv4 0/7] Per route TCP options support kill switches Gilad Ben-Yossef
2009-10-29 8:29 ` David Miller
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=4AE853A5.3060804@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=gilad@codefidence.com \
--cc=netdev@vger.kernel.org \
--cc=ori@comsleep.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).