Lines Matching full:and
16 * code. The TCP/IP code and the application program both run in the same
17 * thread. The sequential API has a much higher overhead and is not very
23 * development is somewhat harder and application programs written for
26 * code size and memory usage.
34 * TCP and UDP), the latter refers to processing raw Ethernet or IP data
38 * (input and output) as well as timer processing (TCP mainly) is done
43 * Non thread-safe APIs, callback style for maximum performance and minimum
58 * to be used without an operating system that implements zero-copy send and
71 * code and the application program must reside in different execution
112 * * Add sys_mbox_trypost_fromisr() and tcpip_callbackmsg_trycallback_fromisr()
114 * * socket API: support poll(), sendmsg() and recvmsg(); fix problems on close
154 * timer IRQ and ethernet IRQ from each other, assuming these may be nested.
164 * In OS mode, @ref callbackstyle_api AND @ref sequential_api can be used.
180 * @ref LOCK_TCPIP_CORE() and @ref UNLOCK_TCPIP_CORE().
187 * DMA-capable ethernet hardware and zero-copy RX
192 * and need to be flushed before the memory is handed over to the
200 * DMA-capable ethernet hardware and cacheline alignment
202 * Nice description about DMA capable hardware and buffer handling:
204 * Read especially sections "Cache coherency" and "Buffer alignment".
226 * context and put them into a queue which is processed from mainloop.\n
228 * Porting: implement all functions in @ref sys_time, @ref sys_prot and
239 * use an RTOS that correctly handles priority inversion and
243 * and all @ref sequential_api.
248 A truly complete and generic sequence for initializing the lwIP stack
253 We assume a configuration using a single Ethernet netif and the
254 UDP and TCP transport layers, IPv4 and the DHCP client.
258 - lwip_init(): Initialize the lwIP stack and all of its subsystems.
262 netif and pass a pointer to this structure as the first argument.
292 the current state. Having link up and link down events is optional but
293 DHCP and IPv6 discover benefit well from those events.
317 * from pbuf- and memory management functions). Application threads using
334 * since they are protected by @ref SYS_LIGHTWEIGHT_PROT and/or
342 * If @ref SYS_LIGHTWEIGHT_PROT is set to 1 and
356 * See the example sys_arch.c files in unix and Win32 port
359 * In short: Copy the functions sys_mark_tcpip_thread() and
360 * sys_check_core_locking() to your port and modify them to work with your OS.
361 * Then let @ref LWIP_ASSERT_CORE_LOCKED() and @ref LWIP_MARK_TCPIP_THREAD()
364 * If you use @ref LWIP_TCPIP_CORE_LOCKING, you also need to copy and adapt
365 * the functions sys_lock_tcpip_core() and sys_unlock_tcpip_core().
366 * Let @ref LOCK_TCPIP_CORE() and @ref UNLOCK_TCPIP_CORE() point
381 assembly or inline replacements for htons() and htonl()
385 If you \#define them to htons() and htonl(), you should
391 hardware isn't serviced frequently and fast enough
398 to match your application and network.