Re: Flood pings and memory leaks
Re: Flood pings and memory leaks
- Subject: Re: Flood pings and memory leaks
- From: Vincent Lubet <email@hidden>
- Date: Thu, 13 Jun 2002 14:59:24 -0700
Here are some tools to watch kernel memory leaks for network related
operations:
1) Use "netstat -m" for mbuf usage;
2) Use "netstat -an" for sockets/control blocks usage;
3) Use zprint for all the kernel memory zones.
Vincent
On Thursday, June 13, 2002, at 02:09 PM, Mike Dolan wrote:
While testing our NKE with 3000 byte flood pings, we ran out of memory
and
found a leak in our code. After fixing the leak, we tested again and
saw
memory still slowly going away. We are using top to watch memory,
specifically, the line that says PhysMem... free x, combined with the
VM...
pageouts data. It's the x next to free that we watch go down and down
and
down. We seem to lose the memory whenever pings get dropped. We can
really
watch it go down when we do another ping flood on the same hub and
have many
collisions causing a rapid loss of pings.
So as a test, we ran the system without our NKE and saw that same
thing. To
further isolate the systems, we've tried it using just a cross-over
cable.
Same results. We have noticed that the responder to the pings doesn't
have
the apparent memory loss.
Two questions,
1. is top the best utility to use to watch kernel memory?
2. is there possibly a leak in ping/MacOS X IP stack? Can anyone else
duplicate our findings?
FYI, running MacOS X 10.1.5 on an iBook with 128MB, new 700MHz iMac
with
256MB and a 400Mhz G4 desktop with 512MB.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.