"(tNetTask): arpresolve: can't allocate llinfo0x3d57e18"
I can't tell if there are packets drop because of this, but my
system continues to handle about 1000 messages per second.
Any idea what causes the tNetTask to complain? Does this
have to do with the pool sizes?
TIA.
Yi Qin
1. The default network stack system memory pool used for
routes,sockets...is too small.
2. The vxWorks target has a misconfigured route table.
3. Calling a function like etherAddrResolve to resolve non-local
addresses
Hope this helps
Alex
"Yi Qin" <y...@ss8networks.com> wrote in message news:<9r6tou$co5$1...@news.storm.ca>...
BT
That is correct. Read section 4.6.3 of the VxWorks Network Programmer's
Guide carefully, use netStackDataPoolShow() and netStackSysPoolShow() to
help work out what your buffer usage is and adjust the pool sizes as
needed. I do that by editing the tables in
target/src/config/usrNetwork.c, but there may be a way of doing this from
the GUI if that's how you build your projects (we just use make).
- Andrew
--
Perfection is reached, not when there is no longer anything to add,
but when there is no longer anything to take away.
- Antoine de Saint-Exupery