|Subject:||Re: [lwip-users] prioritizing of active connections|
|Date:||Sat, 24 Sep 2016 12:58:10 +0000|
Doing some "dirty" trick will not help but cause other problems. IwIP can back-fire and
you will get unpredictable results. Problems that can be difficult to find.
sys_timeout is an LwIP function that runs inside the context of LwIP. Time interval is in milliseconds.
That means that if you set it to 100ms it will call your function (only once) when time elapses.
So instead of using the poll call back that is triggered at best every 0.5 seconds ... you can set your
own timeout function that will handle some house keeping at a faster rate. Do remember that if you
need it to periodically do something you need to set it again and again... until you finish the process.
From: lwip-users <lwip-users-bounces+address@hidden> on behalf of Norbert Kleber <address@hidden>
Sent: Saturday, September 24, 2016 11:20 AM
Subject: Re: [lwip-users] prioritizing of active connections
thank you for your suggestion. I guess I will start with an OS for the next project. For this one it's allready to late I am afraid (thesis due date next month). I didn't fully understand the explanation in the wiki regarding the sys_timeout(TMR_INTERVAL, function , NULL); function. Which timer triggers this function and how can i calculate the exact timing of the sys_timeout?
For now i found an quick and dirty approach which i can't recommand to anyone. I just call 2x tcp_tmr() directly after my computing work is done. This improves my performance. Where i needed 36 seconds for one run I now only need 16 seconds.
Am 23.09.2016 um 18:30 schrieb Noam Weissman:
|[Prev in Thread]||Current Thread||[Next in Thread]|