ps doesn't show threads, it shows processes. Under Linux, there's an option (-m) that shows the threads too (which is possible since L uses processes for it's threads).
Basically, ntop runs one process per NIC and one for processing the packets. There are others, but they run much less often (periodic like purge or as needed like DNS address resolution). If the packet processor is busy, the packet is added to a memory ring buffer (CONST_PACKET_QUEUE_LENGTH in globals-defines.h, check the info.html stats) and processed when the current packet is done. Packets can be lost there (w/o a trace, which should be corrected) - see pbuf.c around lines 1660ff. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David Touitou Sent: Monday, October 20, 2003 6:04 PM To: [EMAIL PROTECTED] Subject: Re: [Ntop] Dropped by the kernel Craig Humphrey wrote: > Hi David, Hi Graig. > Bummer. Getting mad here 8-/ > If you run top, what % of CPU usage is System? Currently (with new buffer size) : less than 4% system arround 1.2% interrupt arround 16.3% user arround 24% for ntop process > Not sure about ntop and SMP, though since it's multithreaded, it probably > does see some benefits. It is but I don't see the other threads... David. _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
