Chronological Thread 

< Chronological >      < Thread >

---

Michael,
Thanks for you help.

By caps-limited I mean the hardware is limited by the number
of calls per second it can process (which is determined by
the number of packets it receives). When it receives too
many packets (which result in too many call attempts) it
fails to produce all the calls required. I've written below
"losses packets" which is not clear - I've meant the
application layer can't handle the load and does not process
all the packets.
I'll try and see what I can do about the rate control. The
windows application is thread safe, and seems to perform
fine beside the rate limit issue.

thanks,
Eli.


>Hi Elie,
>
>comments in-line.
>
>Best regards
>Michael
>
>On Jun 1, 2008, at 4:16 PM, elie wrote:
>
>> Hi,
>>
>> I've built a windows application using SCTP lib which
>> communicates with other hardware (which uses a different
>> SCTP implementation), and I'm having two questions about
>> sctp_send and the sctp_eventloop functions.
>>
>> The hardware I'm communicating is CAPS-limited. It can
>What does "CAPS-limited" mean?
>>
>> handle about 100 messages per the configuration I'm
>> working. So, the windows application is calling sctp_send
>> exactly 100 times a second.
>>
>> The problem is that the SCTP packets are not sent
>> immediately - there are bursts where it reaches a much
>> higher capacity (about 300 messages per second) and a
>> second later it's slowing down almost to none (viewed via
>> wireshark IO graph option). Although the average is 100,
>> the hardware cannot handle a burst of 300 messages and
>> losses packets. And my question is - is there a way to
>> control the sctp_send rate?
>No. There are mechanisms (flow control and congestion
>control) which affect the sending rate. If you want an
>absolute maximum you have to implement it.
>>
>>
>> About the windows application - it's a multithreaded
>> application, where there's a master thread calling
>> sctp_eventLoop in the background (i've followed the
>> sctpapi implementation).
>I hope you do the appropriate locking, since the sctplib
>itself is not multithread capable.
>>
>>
>> My second issue is the master thread: once I want to
>> cleanup everything, the master thread is blocked with
>> sctp_eventLoop, and I need to close it - e.g. to get out
>> of sctp_eventLoop - (I don't want to use ExitThread).
>> What is the proper way of doing it?
>I would close all associations and then quit the
>>application...
>>
>> thanks,
>> Eli.
>>
>>
>> _______________________________________________
>> sctp-discussion mailing list
>> sctp-discussion AT sctp.de
>> http://www.sctp.de/mailman/listinfo/sctp-discussion
>>
>

---

• [SCTP-Discussion] sctp_send timing and sctp_eventLoop, elie, 06/01/2008
  • Re: [SCTP-Discussion] sctp_send timing and sctp_eventLoop, Michael Tuexen, 06/01/2008
  • <Possible follow-up(s)>
  • Re: [SCTP-Discussion] sctp_send timing and sctp_eventLoop, elie, 06/02/2008

---

Archive powered by MHonArc 2.6.19+.