-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why the drop count doesn't work ? #686
Comments
You can try to enable additional debugging output if you uncomment lines with |
@gshimansky Ok,thanks.I'll try. |
From your log I see that there is likely a problem with allocation. New packets cannot be created and this may mean that |
@gshimansky Not only there,but all of this log doesnt have the drop count info.Even at the starting of this program,there is enough mempool space ,but still no drop count. |
In this case I suppose the problem is with allocation. All memory pools are overflowing and new mbufs cannot be created for received packets. What does your graph do? Are you storing packets somewhere? They all have to be either sent to dropped to allow memory reuse. |
My packets are saved in memory,maybe jumped out of the nff-go graph. I can not statistics the packet info in the graph because the operations I do is too slow,so I handle it by myself.I save the information I need to a struct in nff-go handler and then handle it in my own function. |
I am not sure I understand what you have done. If you can paste a code here we can help you. |
All I do is in the globalHandler Function,to save packets in a map by its 5tuple.
|
I write a demo to handle the packet to flow,the packet speed I receive is about 1.7M pps,but I ran this one night,there is the log ,the capture speed is low down but the drop info not print.
you can see that the speed has low down from 1.7M pps to 20k pps,but there is still no drop info,why?
my init code as present,and all work I do is in globalHandler function,just save the pkt to map according to the 5 tuples.
The text was updated successfully, but these errors were encountered: