Read the log - look for the THREADMGMT messages. They show thread creation and WHAT each thread is.
-----Burton -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Enrico Sent: Thursday, November 10, 2011 8:26 AM To: [email protected] Subject: [Ntop] ntop - set cpu affinity for data collection thread Hello we have seen that the snort-daq module, that comes with pfring, can bind the data acquistion process to a particular cpu subset with the 'sched_setaffinity (2)' function. This is really useful for reducing interrupts handling time in our system We would like to be able to do the same thing also for ntop. Unlike snort we see that it is an high parallelized application and usually creates almost 10 threads when starts. Using Taskset would bind all the 10 threads to a single cpu, but brings to resources competition between ntop threads on the same core which increases a lot the context switching time. Is there a way to know what is the data acquisition/collection thread for a ntop instance that actually handles the packets coming from the kernel? Looking at ntop logs for example only shows what is the father process creating that thread. Any suggestion? Thanks in advance. Enrico. _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
