Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Feb 2013 10:37:54 +0800
From:      Sepherosa Ziehau <sepherosa@gmail.com>
To:        Lawrence Stewart <lstewart@room52.net>
Cc:        Andre Oppermann <andre@freebsd.org>, John Baldwin <jhb@freebsd.org>, "freebsd-net@freebsd.org" <net@freebsd.org>
Subject:   Re: [PATCH] Add a new TCP_IGNOREIDLE socket option
Message-ID:  <CAMOc5cxgpi6MVcJBDDt8cwTdScU3O=NT22TH_YC7bfgxu5Y02g@mail.gmail.com>
In-Reply-To: <51242B05.1040003@room52.net>
References:  <201301221511.02496.jhb@freebsd.org> <511B4DEF.8000500@freebsd.org> <511B6A87.5060000@freebsd.org> <511BA29E.5050501@freebsd.org> <511BA7D9.3050709@freebsd.org> <511C3FB8.40506@freebsd.org> <51242B05.1040003@room52.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 20, 2013 at 9:46 AM, Lawrence Stewart <lstewart@room52.net> wrote:
> *crickets chirping*
>
> Time to move this discussion forward...
>
>
> If any robust counter-arguments exist, now is the time for us to hear
> them. I haven't read anything thus far which convinces me that we should
> not provide knobs to tune our stack's dynamics.
>
> In the absence of any compelling counter-arguments, I would like to
> propose the following:
>
> - We rename the net.inet.tcp.experimental sysctl node introduced in
> r242266 for IW10 support to net.inet.tcp.nonstandard, and re-parent the
> initcwnd10 sysctl under this node.
>
> - We introduce a new net.inet.tcp.nonstandard.allowed sysctl variable
> and default it to 0. Only when it is changed to 1 will we allow starkly
> non standards compliant behaviour to be enabled in the stack. As a more
> complex but expressive alternative, we can make the sysctl take a bit
> mask or CSV string which specifies which non-standard options the sys
> admin permits (I'd prefer this as we can easily test non-standard
> options like IW10 in head without blanket enabling all non standard
> behaviour).
>
> - We introduce a new net.inet.tcp.nonstandard.noidlereset sysctl
> variable, and use it to enable/disable window-reset-after-idle behaviour
> as proposed by John.
>
> - We don't introduce a TF_IGNOREIDLE sockopt, and instead introduce a
> more generic sockopt and/or mechanism for per-application tuning of all
> options which affect stack dynamics (both standard and non-standard
> options). I'm open to suggestions on what this could/should look like.

Lawrence,

A route metric?  BTW, as for IW10, it could also become a route metric
(as proposed by the draft author's presentation
http://www.ietf.org/proceedings/79/slides/tcpm-0.pdf)


John,

I came across this draft several days ago, you may be interested:
http://tools.ietf.org/html/draft-ietf-tcpm-newcwv-00

This one is a bit old, but it is still interesting to read (cited by
the above draft):
http://tools.ietf.org/html/draft-hughes-restart-00


Best Regards,
sephe

--
Tomorrow Will Never Die



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMOc5cxgpi6MVcJBDDt8cwTdScU3O=NT22TH_YC7bfgxu5Y02g>