I haven't heard of this, but it seems like a good idea. I recently was in a
wild chase where NetLibSend was timing out because of lack of memory.
Presumably it was "waiting" for send queues to drain and free up buffer
space. There were no writes outstanding so it wasn't going to happen. The
moral, don't run NetLib with less than 2Kb of heap free.
LL
At 09:40 AM 10/8/99 -0700, Jeff Ishaq wrote:
>Isn't there some setting somewhere that will tell Netlib to use the storage
>heap to some extent? I'm trying to streamline our dynamic memory
>consumption (gee, doesn't that sound familiar?). I seem to remember
>something that would tell Netlib to use the storage heap to allocate its
>packets, as oppose to the dynamic heap. Was this one of many late-night
>hallucinations I had reading the SDK dox, or is there really some way to do
>this?
>
>Thanks,
>-Jeff
