Lines Matching full:can

14 lwIP functionality, multiple threads support can be implemented in the
16 functionality. Timer scheduling is implemented in lwIP, but can be implemented
24 Semaphores can be either counting or binary - lwIP works with both
26 to be posted (implementing as a rendez-vous point where only one message can be
27 posted at a time can have a highly negative impact on performance). A message
38 required for such types can be either allocated in place (globally or on the
50   points to (which can be both a pointer or the actual OS structure).
99   points to (which can be both a pointer or the actual OS structure).
110   Blocks the thread until the mutex can be grabbed.
179   To allow for efficient implementations, this can be defined as a
249 mem_malloc() you can run into a circular function call problem. In mem.c
251 can't be performed when sys_arch uses mem_malloc.
290   Measurement calls made throughout lwip, these can be defined to nothing.