sys_arch.txt 9.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228
  1. sys_arch interface for lwIP 0.6++
  2. Author: Adam Dunkels
  3. The operating system emulation layer provides a common interface
  4. between the lwIP code and the underlying operating system kernel. The
  5. general idea is that porting lwIP to new architectures requires only
  6. small changes to a few header files and a new sys_arch
  7. implementation. It is also possible to do a sys_arch implementation
  8. that does not rely on any underlying operating system.
  9. The sys_arch provides semaphores and mailboxes to lwIP. For the full
  10. lwIP functionality, multiple threads support can be implemented in the
  11. sys_arch, but this is not required for the basic lwIP
  12. functionality. Previous versions of lwIP required the sys_arch to
  13. implement timer scheduling as well but as of lwIP 0.5 this is
  14. implemented in a higher layer.
  15. In addition to the source file providing the functionality of sys_arch,
  16. the OS emulation layer must provide several header files defining
  17. macros used throughout lwip. The files required and the macros they
  18. must define are listed below the sys_arch description.
  19. Semaphores can be either counting or binary - lwIP works with both
  20. kinds. Mailboxes are used for message passing and can be implemented
  21. either as a queue which allows multiple messages to be posted to a
  22. mailbox, or as a rendez-vous point where only one message can be
  23. posted at a time. lwIP works with both kinds, but the former type will
  24. be more efficient. A message in a mailbox is just a pointer, nothing
  25. more.
  26. Semaphores are represented by the type "sys_sem_t" which is typedef'd
  27. in the sys_arch.h file. Mailboxes are equivalently represented by the
  28. type "sys_mbox_t". lwIP does not place any restrictions on how
  29. sys_sem_t or sys_mbox_t are represented internally.
  30. The following functions must be implemented by the sys_arch:
  31. - void sys_init(void)
  32. Is called to initialize the sys_arch layer.
  33. - sys_sem_t sys_sem_new(u8_t count)
  34. Creates and returns a new semaphore. The "count" argument specifies
  35. the initial state of the semaphore.
  36. - void sys_sem_free(sys_sem_t sem)
  37. Deallocates a semaphore.
  38. - void sys_sem_signal(sys_sem_t sem)
  39. Signals a semaphore.
  40. - u32_t sys_arch_sem_wait(sys_sem_t sem, u32_t timeout)
  41. Blocks the thread while waiting for the semaphore to be
  42. signaled. If the "timeout" argument is non-zero, the thread should
  43. only be blocked for the specified time (measured in
  44. milliseconds). If the "timeout" argument is zero, the thread should be
  45. blocked until the semaphore is signalled.
  46. If the timeout argument is non-zero, the return value is the number of
  47. milliseconds spent waiting for the semaphore to be signaled. If the
  48. semaphore wasn't signaled within the specified time, the return value is
  49. SYS_ARCH_TIMEOUT. If the thread didn't have to wait for the semaphore
  50. (i.e., it was already signaled), the function may return zero.
  51. Notice that lwIP implements a function with a similar name,
  52. sys_sem_wait(), that uses the sys_arch_sem_wait() function.
  53. - sys_mbox_t sys_mbox_new(int size)
  54. Creates an empty mailbox for maximum "size" elements. Elements stored
  55. in mailboxes are pointers. You have to define macros "_MBOX_SIZE"
  56. in your lwipopts.h, or ignore this parameter in your implementation
  57. and use a default size.
  58. - void sys_mbox_free(sys_mbox_t mbox)
  59. Deallocates a mailbox. If there are messages still present in the
  60. mailbox when the mailbox is deallocated, it is an indication of a
  61. programming error in lwIP and the developer should be notified.
  62. - void sys_mbox_post(sys_mbox_t mbox, void *msg)
  63. Posts the "msg" to the mailbox. This function have to block until
  64. the "msg" is really posted.
  65. - err_t sys_mbox_trypost(sys_mbox_t mbox, void *msg)
  66. Try to post the "msg" to the mailbox. Returns ERR_MEM if this one
  67. is full, else, ERR_OK if the "msg" is posted.
  68. - u32_t sys_arch_mbox_fetch(sys_mbox_t mbox, void **msg, u32_t timeout)
  69. Blocks the thread until a message arrives in the mailbox, but does
  70. not block the thread longer than "timeout" milliseconds (similar to
  71. the sys_arch_sem_wait() function). If "timeout" is 0, the thread should
  72. be blocked until a message arrives. The "msg" argument is a result
  73. parameter that is set by the function (i.e., by doing "*msg =
  74. ptr"). The "msg" parameter maybe NULL to indicate that the message
  75. should be dropped.
  76. The return values are the same as for the sys_arch_sem_wait() function:
  77. Number of milliseconds spent waiting or SYS_ARCH_TIMEOUT if there was a
  78. timeout.
  79. Note that a function with a similar name, sys_mbox_fetch(), is
  80. implemented by lwIP.
  81. - u32_t sys_arch_mbox_tryfetch(sys_mbox_t mbox, void **msg)
  82. This is similar to sys_arch_mbox_fetch, however if a message is not
  83. present in the mailbox, it immediately returns with the code
  84. SYS_MBOX_EMPTY. On success 0 is returned.
  85. To allow for efficient implementations, this can be defined as a
  86. function-like macro in sys_arch.h instead of a normal function. For
  87. example, a naive implementation could be:
  88. #define sys_arch_mbox_tryfetch(mbox,msg) \
  89. sys_arch_mbox_fetch(mbox,msg,1)
  90. although this would introduce unnecessary delays.
  91. - struct sys_timeouts *sys_arch_timeouts(void)
  92. Returns a pointer to the per-thread sys_timeouts structure. In lwIP,
  93. each thread has a list of timeouts which is repressented as a linked
  94. list of sys_timeout structures. The sys_timeouts structure holds a
  95. pointer to a linked list of timeouts. This function is called by
  96. the lwIP timeout scheduler and must not return a NULL value.
  97. In a single thread sys_arch implementation, this function will
  98. simply return a pointer to a global sys_timeouts variable stored in
  99. the sys_arch module.
  100. If threads are supported by the underlying operating system and if
  101. such functionality is needed in lwIP, the following function will have
  102. to be implemented as well:
  103. - sys_thread_t sys_thread_new(char *name, void (* thread)(void *arg), void *arg, int stacksize, int prio)
  104. Starts a new thread named "name" with priority "prio" that will begin its
  105. execution in the function "thread()". The "arg" argument will be passed as an
  106. argument to the thread() function. The stack size to used for this thread is
  107. the "stacksize" parameter. The id of the new thread is returned. Both the id
  108. and the priority are system dependent.
  109. - sys_prot_t sys_arch_protect(void)
  110. This optional function does a "fast" critical region protection and returns
  111. the previous protection level. This function is only called during very short
  112. critical regions. An embedded system which supports ISR-based drivers might
  113. want to implement this function by disabling interrupts. Task-based systems
  114. might want to implement this by using a mutex or disabling tasking. This
  115. function should support recursive calls from the same task or interrupt. In
  116. other words, sys_arch_protect() could be called while already protected. In
  117. that case the return value indicates that it is already protected.
  118. sys_arch_protect() is only required if your port is supporting an operating
  119. system.
  120. - void sys_arch_unprotect(sys_prot_t pval)
  121. This optional function does a "fast" set of critical region protection to the
  122. value specified by pval. See the documentation for sys_arch_protect() for
  123. more information. This function is only required if your port is supporting
  124. an operating system.
  125. Note:
  126. Be carefull with using mem_malloc() in sys_arch. When malloc() refers to
  127. mem_malloc() you can run into a circular function call problem. In mem.c
  128. mem_init() tries to allcate a semaphore using mem_malloc, which of course
  129. can't be performed when sys_arch uses mem_malloc.
  130. -------------------------------------------------------------------------------
  131. Additional files required for the "OS support" emulation layer:
  132. -------------------------------------------------------------------------------
  133. cc.h - Architecture environment, some compiler specific, some
  134. environment specific (probably should move env stuff
  135. to sys_arch.h.)
  136. Typedefs for the types used by lwip -
  137. u8_t, s8_t, u16_t, s16_t, u32_t, s32_t, mem_ptr_t
  138. Compiler hints for packing lwip's structures -
  139. PACK_STRUCT_FIELD(x)
  140. PACK_STRUCT_STRUCT
  141. PACK_STRUCT_BEGIN
  142. PACK_STRUCT_END
  143. Platform specific diagnostic output -
  144. LWIP_PLATFORM_DIAG(x) - non-fatal, print a message.
  145. LWIP_PLATFORM_ASSERT(x) - fatal, print message and abandon execution.
  146. Portability defines for printf formatters:
  147. U16_F, S16_F, X16_F, U32_F, S32_F, X32_F, SZT_F
  148. "lightweight" synchronization mechanisms -
  149. SYS_ARCH_DECL_PROTECT(x) - declare a protection state variable.
  150. SYS_ARCH_PROTECT(x) - enter protection mode.
  151. SYS_ARCH_UNPROTECT(x) - leave protection mode.
  152. If the compiler does not provide memset() this file must include a
  153. definition of it, or include a file which defines it.
  154. This file must either include a system-local <errno.h> which defines
  155. the standard *nix error codes, or it should #define LWIP_PROVIDE_ERRNO
  156. to make lwip/arch.h define the codes which are used throughout.
  157. perf.h - Architecture specific performance measurement.
  158. Measurement calls made throughout lwip, these can be defined to nothing.
  159. PERF_START - start measuring something.
  160. PERF_STOP(x) - stop measuring something, and record the result.
  161. sys_arch.h - Tied to sys_arch.c
  162. Arch dependent types for the following objects:
  163. sys_sem_t, sys_mbox_t, sys_thread_t,
  164. And, optionally:
  165. sys_prot_t
  166. Defines to set vars of sys_mbox_t and sys_sem_t to NULL.
  167. SYS_MBOX_NULL NULL
  168. SYS_SEM_NULL NULL