mirror
/
esp-idf
kopia lustrzana https://github.com/espressif/esp-idf
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność
esp-idf/components/lwip/Kconfig

30 wiersze
720 B
Plaintext
Czysty Zwykły widok Historia

Initial public version
2016-08-17 15:08:22 +00:00
menu "LWIP"
config LWIP_MAX_SOCKETS
lwip: rework comments according to review
2016-10-28 05:35:06 +00:00
int "Max number of open sockets"
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
range 1 16
default 4
help
Sockets take up a certain amount of memory, and allowing fewer
sockets to be open at the same time conserves memory. Specify
lwip: rework comments according to review
2016-10-28 05:35:06 +00:00
the maximum amount of sockets here. The valid value is from 1
to 16.
Initial public version
2016-08-17 15:08:22 +00:00
'Merge branch 'thread_local_storage_delete_callbacks' into 'master' The thread-local-storage feature in FreeRTOS attaches an application-usable array of pointers to a thread control block. These pointers usually point to a structure the thread allocates. When a thread gets (voluntarily or involuntarily) destroyed, this memory can leak. This merge adds a matching second array of user-settable pointers to destructor routines. As soon as the task gets cleaned up (which happens in the idle thread), the destructors get called and the memory can be freed. See merge request !19
2016-08-24 05:29:06 +00:00
config LWIP_THREAD_LOCAL_STORAGE_INDEX
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
int "Index for thread-local-storage pointer for lwip"
default 0
help
Specify the thread-local-storage-pointer index for lwip
use.
'Merge branch 'thread_local_storage_delete_callbacks' into 'master' The thread-local-storage feature in FreeRTOS attaches an application-usable array of pointers to a thread control block. These pointers usually point to a structure the thread allocates. When a thread gets (voluntarily or involuntarily) destroyed, this memory can leak. This merge adds a matching second array of user-settable pointers to destructor routines. As soon as the task gets cleaned up (which happens in the idle thread), the destructors get called and the memory can be freed. See merge request !19
2016-08-24 05:29:06 +00:00
components/lwip: make SO_REUSE configurable via menuconfig Not all environments need or can work with SO_REUSE enabled, so making this option configurable.
2016-09-20 07:36:55 +00:00
config LWIP_SO_REUSE
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Enable SO_REUSEADDR option"
default 0
help
Enabling this option allows binding to a port which remains in
TIME_WAIT.
components/lwip: make SO_REUSE configurable via menuconfig Not all environments need or can work with SO_REUSE enabled, so making this option configurable.
2016-09-20 07:36:55 +00:00
Initial public version
2016-08-17 15:08:22 +00:00
endmenu