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

About NC_REVERSE_QUEUE param #457

Open
sourcema opened this issue Jan 30, 2024 · 3 comments
Open

About NC_REVERSE_QUEUE param #457

sourcema opened this issue Jan 30, 2024 · 3 comments
Labels
is:question Issue is actually a question.

Comments

@sourcema
Copy link

I found that the parameter setting value in the file(session_p.h) is 5. What is the reason for this? Will there be any problems if a large number of devices are connected concurrently?

@michalvasko
Copy link
Member

Why the interest in a random internal macro, have you checked where it is used? In short, ignore it, it is extremely unlikely it will affect you in any way.

@michalvasko michalvasko added the is:question Issue is actually a question. label Jan 31, 2024
@sourcema
Copy link
Author

Why the interest in a random internal macro, have you checked where it is used? In short, ignore it, it is extremely unlikely it will affect you in any way.

The reason why I became interested in it is because we encountered the problem of tcp accept queue overflow. This parameter affects the size of the full connection queue, so I want to know what is the basis for setting this value?

@michalvasko
Copy link
Member

I see, there is no special reason for the value. When implementing it (a long time ago) I saw 3 being used so I opted for a bit higher number to be safe. As long as you application is accepting new connections often enough, I do not think the queue can ever reach the limit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:question Issue is actually a question.
Projects
None yet
Development

No branches or pull requests

2 participants