Many thanks for your earlier reply. Though the load is not shared evenly I got a setting combining both FlowDir and RSS that does a decent job. I am dealing with packets at national gateway. Hence there are many encapsulating headers like pseudowire, PPP,VLAN, MPLS etc...so the hardware obviously is at a loss to parse all that and get to IP or TCP headers. Hence the fallback to queue 0 ( from both FlowDir and RSS ) which is getting a high amount of traffic in comparison. Hopefully I can distribute packets to cores/queues in a round robin fashion with a hack in ixgbe. I don't need to track flows ( that will be done in userspace ), just packets are fine spread across CPUs.
Who is supposed to set the timestamp on packets ? I can see all packets with time offset 0. Is it ixgbe / pf_ring / userland . gettimeofday() is very costly from userspace. This is slowing down pfcount processing in my case I think( but I need to verify that ) Also I found PF_RING pfring_open_multichannel() to create too many threads (72 )for any number of RSS settings on a 32-cpu machine running kernel 2.6.38 with MQ=1,1 RSS=8,8 FlowDir=1,1 Regards, Soumyendra
_______________________________________________ Ntop-misc mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-misc
