Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces two key changes:
0
to disable theIP_TOS
socket option.tos
, allowing TOS to be set on a per-socket basis. If this parameter is set, it overrides the global value.Details
Previously, the global
TOS
parameter could not be set to0
, meaning that disabling theIP_TOS
socket option was not straightforward. This PR introduces the ability to explicitly setTOS=0
, ensuring that noIP_TOS
is applied.Additionally, this PR introduces a new per-socket
tos
parameter, which enables granular control over TOS settings on an individual socket level. If a socket-specific value is provided, it takes precedence over the global setting, allowing for more flexible traffic prioritization configurations.Solution
0
as a valid value.tos
parameter in the socket configuration.tos
value is set, it overrides the global TOS setting.Compatibility
TOS=0
does not affect existing deployments but provides more flexibility.tos
parameter is an additional feature that does not interfere with existing configurations.