User`s guide

52
K
A
DAK
KwikNet System Configuration
General Stack Parameters (continued)
KwikNet Optimization
The KwikNet Library can be optimized for speed or size. In general, speed improvement
comes at the expense of increased code size. Conversely, reducing the memory footprint
usually imposes an execution speed penalty. You can choose your optimization
preference from the pull down list.
KwikNet Shutdown
Most embedded applications which incorporate a network stack operate forever once
started. In some cases however, especially when testing, it may be desirable to permit the
network stack to shut down in an orderly fashion. If you plan to call KwikNet function
kn_exit() to shut down KwikNet, check this box. Otherwise, leave this box unchecked
and all of the shutdown code will be omitted, thereby reducing the memory footprint.
Warning!
You must not shut down KwikNet unless KwikNet's memory
is allocated from a static array or from a fixed region of
memory acquired when KwikNet is started and released
when KwikNet is stopped.