RTCS stores internet packets in an RTCS_PCB. A PCB will be required for each simultaneous incoming or outgoing packet RTCS processes. You can control the number of PCBs RTCS will allocate by setting _RTCSPCB_init, _RTCSPCB_grow and _RTCSPCB_max. Init represents the initial number of PCBs RTCS will allocate, grow represents the additional number of PCBs which will be allocated if the PCBs are exhausted, and max represents the upper bound of PCBs. Max may be set to zero to indicate that there is no upper bound.
RTCS receives API requests and incoming packets encapsulated in messages. _RTCS_msgpool_init , _RTCS_msgpool_grow and _RTCS_msgpool_max are used to control the number of messages RCTS requires. You will need one message per simultaneous receive packet processed by RTCS, plus one message per application task using RTCS (and that includes any of the RTCS supplied application tasks such as telnet or FTP).
The total number of sockets can be controlled in a similar manner by using _RTCS_socket_part_init , _RTCS_socket_part_grow and _RTCS_socket_part_max.
