|
From: | Karsten Koop |
Subject: | [lwip-users] MEMP_NUM_SYS_TIMEOUT after update to latest release 2.2.0 |
Date: | Mon, 6 May 2024 16:07:20 +0200 |
User-agent: | Mozilla Thunderbird |
Hello, I'm trying to update from lwip 2.1.2 to newest stable 2.2.0, and I'm seeing some changes in the mDNS part. It seems with the newer version additional timeouts are used, and accordingly MEMP_NUM_SYS_TIMEOUT would have to be increased. In mdns.c, I now find the comment * You need to increase MEMP_NUM_SYS_TIMEOUT by one if you use MDNS! at the top. But increasing the value by one was not sufficient, I ran into an assertion in timeouts.c:190. Increasing MEMP_NUM_SYS_TIMEOUT by 3 seems to work, but it doesn't feel right to just increase until it works. I also found what seems to be the mail exchange about the pull request, where it's stated (https://savannah.nongnu.org/patch/?9523#comment18): > Because a lot of different timeouts are needed, you need to increase the MEMP_NUM_SYS_TIMEOUT with 8. Is this the correct value? Or is there any other documentation on how many additional timeouts are required? I also wonder if the calculation LWIP_NUM_SYS_TIMEOUT_INTERNAL could already take this into account, currently it seems LWIP_MDNS_RESPONDER is not considered there. Kind regards, |
[Prev in Thread] | Current Thread | [Next in Thread] |