Skip to content
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

Packets are dropped due to overlimits #3

Open
forkingmaster opened this issue Apr 25, 2019 · 3 comments
Open

Packets are dropped due to overlimits #3

forkingmaster opened this issue Apr 25, 2019 · 3 comments

Comments

@forkingmaster
Copy link

forkingmaster commented Apr 25, 2019

Hi @vcgomes,

In the recent times, I see that UDP packets are being dropped in kernel due to overlimits. I was reading a bit to understand the term "overlimits" in tc qdisc. From the study I infer that, it is the delay caused by qdisc and that's the reason packets are dropped when the txtime expires waiting in queue to be dequeued. Am I right? Or correct me if am wrong?

image

May I know why this scenario comes in?

@vcgomes
Copy link
Contributor

vcgomes commented Apr 25, 2019

Your understanding is correct.

During development we had a DROP_IF_LATE cmsg flag that we could set per packet to select if that packet was allowed to be dequeued even if late ("expired"). But after a very long discussion with the upstream maintainers, the agreement was to remove that flag and keep this behavior.

From my experience, an increasing "overlimits" usually mean some problem in time synchronization, or that for traffic with lots of "burstiness" that the network card cannot dequeue packets in time.

@forkingmaster
Copy link
Author

I have ensured that time synchronization does not exceed few ns accuracy while the test is being performed. At times, packets do not get dropped or marked as overlimits even when the udp_tai application is running at 100us cycle interval. So I am not able to conclude if burstiness could be the only reason.

What do you think about it?

@forkingmaster
Copy link
Author

@vcgomes, Any clue on what else it could be?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants