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.

Sign up for GitHub

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

Jump to bottom

Optimize TCP loopback #223

Closed
iangudger opened this issue May 1, 2019 · 2 comments
Closed

Optimize TCP loopback #223

iangudger opened this issue May 1, 2019 · 2 comments
Assignees
@iangudger
Labels
area: networking Issue related to networking area: performance Issue related to performance & benchmarks priority: p2 Normal priority type: enhancement New feature or request

Comments

@iangudger
Copy link
Contributor

We currently do full TCP over the loopback. We could significantly improve performance if we directly connected the endpoints and exchanged buffers.
@iangudger iangudger self-assigned this May 1, 2019
@ianlewis ianlewis added area: networking Issue related to networking area: performance Issue related to performance & benchmarks type: enhancement New feature or request priority: p2 Normal priority labels May 3, 2019
@Mikezhangzw
Copy link

do you have any progress in optimization of tcp loopback?

@snyk-bot snyk-bot mentioned this issue Mar 5, 2020
Open
@hbhasker
Copy link
Contributor

This is not the right way to optimize loopback as this will break too many tools where loopback traffic will be invisible to say tcpdump etc. We do not intend to do this. There are other optimizations to improve stack performance in general which are in progress. Going to close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iangudger iangudger

Labels
area: networking Issue related to networking area: performance Issue related to performance & benchmarks priority: p2 Normal priority type: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ianlewis @hbhasker @iangudger @Mikezhangzw