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

Zero-copy in the network stack #25

Open
IanSeyler opened this issue May 27, 2017 · 0 comments
Open

Zero-copy in the network stack #25

IanSeyler opened this issue May 27, 2017 · 0 comments

Comments

@IanSeyler
Copy link
Member

http://en.wikipedia.org/wiki/Zero-copy

This is partially implemented.

b_net_tx forwards the memory location of the packet directly to the network driver and the hardware handles it. No time is spent by the CPU to copy anything.

b_net_rx does one copy (from the OS packet buffer to the requested memory address) via a nasty rep movsb so that will need to be adjusted in the network drivers.

On startup a default OS buffer location will be configured. Via a system call an application will be allowed to modify this to suit its own location.

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

No branches or pull requests

1 participant