[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=FLGM1z0VLH+WZXvF=7TZHtMhxLe+KRF3ojWR1@mail.gmail.com>
Date: Fri, 7 Jan 2011 05:04:58 -0500
From: Syed Obaid Amin <obaidasyed@...il.com>
To: Stephen Hemminger <shemminger@...tta.com>
Cc: netdev@...r.kernel.org
Subject: Re: About disabling congestion control
Thanks for the reply. Yes I also thought to create a sort of NULL
congestion control type that does nothing. But this way the changes
would be system wide. BTW, would some one share the insight that why
linux uses sysctl to select a congestion control algorithm instead of
socket options.
Thanks again,
Obaid
On Thu, Jan 6, 2011 at 8:37 PM, Stephen Hemminger <shemminger@...tta.com> wrote:
> On Thu, 6 Jan 2011 20:25:18 -0500
> Syed Obaid Amin <obaidasyed@...il.com> wrote:
>
>> Hey all,
>>
>> I am currently working on a socket option to disable the tcp
>> congestion control. I think the simplest approach to do this is to
>> ignore cwnd before sending out a packet.
>>
>> After going through tcp output engine it seems that tcp_cwnd_test is
>> the method that decides that how many segments can be sent out on a
>> wire. For testing it out, I changed this method so that if no-cc
>> option is ON, just return a big constant value. But, it didn't work
>> and I am unable to see a burst of pkts. It looks like that I am
>> missing something here.
>>
>> Any suggestions that what is the right place to look for disabling the
>> congestion control ?
>>
>> Thanks much!
>>
>> Obaid
>
> I assume this is just a local hack experiment; not something you
> want to actually submit for other users to use...
>
> The easiest/safest way to do this would be to build/define a new TCP congestion
> control type that does nothing.
>
>
--
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