Collaboration diagram for NETIF:
Modules | |
| Loopback interface | |
Macros | |
| #define | LWIP_NETIF_HOSTNAME 0 |
| #define | LWIP_NETIF_API 0 |
| #define | LWIP_NETIF_REMOVE_CALLBACK 0 |
| #define | LWIP_NETIF_TX_SINGLE_PBUF 0 |
| #define | LWIP_NUM_NETIF_CLIENT_DATA 0 |
Detailed Description
Macro Definition Documentation
| #define LWIP_NETIF_API 0 |
LWIP_NETIF_API==1: Support netif api (in netifapi.c)
| #define LWIP_NETIF_HOSTNAME 0 |
| #define LWIP_NETIF_REMOVE_CALLBACK 0 |
LWIP_NETIF_STATUS_CALLBACK==1: Support a callback function whenever an interface changes its up/down status (i.e., due to DHCP IP acquisition) LWIP_NETIF_LINK_CALLBACK==1: Support a callback function from an interface whenever the link changes (i.e., link down) LWIP_NETIF_REMOVE_CALLBACK==1: Support a callback function that is called when a netif has been removed
| #define LWIP_NETIF_TX_SINGLE_PBUF 0 |
LWIP_NETIF_HWADDRHINT==1: Cache link-layer-address hints (e.g. table indices) in struct netif. TCP and UDP can make use of this to prevent scanning the ARP table for every sent packet. While this is faster for big ARP tables or many concurrent connections, it might be counterproductive if you have a tiny ARP table or if there never are concurrent connections. LWIP_NETIF_TX_SINGLE_PBUF: if this is set to 1, lwIP tries to put all data to be sent into one single pbuf. This is for compatibility with DMA-enabled MACs that do not support scatter-gather. Beware that this might involve CPU-memcpy before transmitting that would not be needed without this flag! Use this only if you need to!
- Todo:
- : TCP and IP-frag do not work with this, yet:
| #define LWIP_NUM_NETIF_CLIENT_DATA 0 |
LWIP_NUM_NETIF_CLIENT_DATA: Number of clients that may store data in client_data member array of struct netif.
Definition at line 1476 of file opt.h.
Referenced by netif_set_link_down().
