Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Feb 2013 19:18:00 +1100
From:      grenville armitage <garmitage@swin.edu.au>
To:        freebsd-net@freebsd.org
Subject:   Re: [PATCH] Add a new TCP_IGNOREIDLE socket option
Message-ID:  <511757B8.3080407@swin.edu.au>
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F700B87@SACEXCMBX01-PRD.hq.netapp.com>
References:  <201301221511.02496.jhb@freebsd.org> <50FF06AD.402@networx.ch> <061B4EA5-6A93-48A0-A269-C2C3A3C7E77C@lakerest.net> <201302060746.43736.jhb@freebsd.org> <511292C9.4040307@mu.org> <E6BF2B74-175F-49D9-B480-8941294D2E19@neville-neil.com> <51166019.9040104@mu.org> <CAN6yY1uX__JDEk9dLdJr3pdE1u848jaF_jTn%2B_mrP05bXqm_Pw@mail.gmail.com> <D4D47BCFFE5A004F95D707546AC0D7E91F700B87@SACEXCMBX01-PRD.hq.netapp.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On 02/10/2013 18:30, Eggert, Lars wrote:
> On Feb 10, 2013, at 6:05, Kevin Oberman <kob6558@gmail.com> wrote:
>> One idea that popped into my head (and may be completely ridiculous,
>> is to make its availability dependent on a kernel option and have
>> warning in NOTES about it contravening normal and accepted practice
>> and that it can cause serious problems both for yourself and for
>> others using the network.
>
> Also, if it gets merged, don't call it TCP_IGNOREIDLE. Call it TCP_BLAST_DANGEROUSLY_AFTER_IDLE.

TCP_AVALANCHE

cheers,
gja




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?511757B8.3080407>