Re: Regarding SCTP_DELAYED_ACK_TIME

[Vlad Yasevich <vladislav.yasevich@hp.com>]

Padmalochan Moharana wrote:
> Hi ,
> 
> Is there any other option to set the SACK timer value?

It is not supported in RHEL4.  You can get support for it
in RHEL5.

The functionality to customize SACK timeout was first
introduced in 2.6.13.  At that time it was settable through
sysctl only.

The API was introduced in lksctp-tools 1.0.6 and the first
kernel to support the API was 2.6.16.

-vlad

> 
> Br,
> Padmalochan
> 
> On Wed, Apr 29, 2009 at 5:58 PM, Vlad Yasevich
> <vladislav.yasevich@hp.com> wrote:
>> Padmalochan Moharana wrote:
>>> Hello,
>>>
>>> In my application I have tried to set the SACK timer to 400 Milli
>>> second by writing following code.
>>>
>>> struct sctp_assoc_value sack_timer ;
>>> bzero(&sack_timer, sizeof(sack_timer));
>>> sack_timer.assoc_id =1 ;
>>> sack_timer.assoc_value = 400 ;
>>> int res = setsockopt(socketFD, IPPROTO_SCTP, SCTP_DELAYED_ACK_TIME,
>>> &sack_timer,sizeof(struct sctp_assoc_value ));
>>>
>>> But setsockopt() returns error ("Protocol not available").
>>>
>>> The kernel version i have used is : 2.6.9-55.EL
>>> lksctp version: 1.0.8
>> This kernel does not support the socket option you are trying to use.
>> You need to upgrade the kernel.
>>
>> -vlad
>>
>>> Please let me know how can i set SCTP_DELAYED_ACK_TIME value in my application.
>>>
>>> Br,
>>> Padmalochan
>>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>