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

ER: adding route "options" beside usual ones #3073

Open
gsustek opened this issue Oct 16, 2024 · 1 comment
Open

ER: adding route "options" beside usual ones #3073

gsustek opened this issue Oct 16, 2024 · 1 comment
Labels

Comments

@gsustek
Copy link

gsustek commented Oct 16, 2024

AWS-CNI Feature Proposal

Is your proposed feature related to a problem?

No.

Describe the feature you'd like

I would like to have additional capability of setting arbitrary options on routes which will be affective upon pod creation.
Specific ip route options of interest is quickack

Proposal i based on following link.
https://man7.org/linux/man-pages/man8/ip-route.8.html - OPTIONS := FLAGS

(Optional) Describe your proposed solution

You should extend route class:

return ip.AddDefaultRoute(gw, dev)

with OPTIONS and possible FLAGS from https://man7.org/linux/man-pages/man8/ip-route.8.html page.

Motivation

Applications running in container often can not be changed programatically but network performance issues can be controlled on kernel level.

The 40ms delay in responding to ACK is an method built into the Linux IP stack to improve network performance.

When a participant in a TCP conversation has an ACK to send, the participant is acknowledging some data that has been received. That receiver will very likey have a reply to the data it just received.

The linux kernel will delay the outgoing ACK by up to 40ms to allow the reply to queue, then send both the reply and the ACK together.

This can be controlled/overide in two ways:

At the application level with the TCP_QUICKACK socket option. See man 7 tcp for further details. This option needs to be set with setsockopt() after each operation of TCP on a given socket.

In newer kernel route level with quickack 1 on the end of a route, eg:
ip route change default via 10.0.0.1 quickack 1

Regards,
Goran.

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days

@github-actions github-actions bot added the stale Issue or PR is stale label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant