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

feature request: support for MSG_ZEROCOPY and MSG_TRUNC flags #1678

Open
bltierney opened this issue Mar 27, 2024 Discussed in #1520 · 2 comments
Open

feature request: support for MSG_ZEROCOPY and MSG_TRUNC flags #1678

bltierney opened this issue Mar 27, 2024 Discussed in #1520 · 2 comments

Comments

@bltierney
Copy link
Contributor

See discussion 1520, and see neper for sample code. https://github.com/google/neper

This will be a little bit of work, as you'll need to use send/recv instead of read/write calls.

Discussed in #1520

Originally posted by rjmcmahon May 17, 2023
Hi,

I'm considering adding 200G+ support to iperf 2 and thought it might be interesting to get iperf 3 engineers' thoughts. One initial question I have is about using sendfile vs the SO_ZEROCOPY/MSG_ZEROCOPY socket/send option. Any thoughts on that?

Also, I'm wondering about BIG TCP and if there have been any experiments with v6 or possibly v4?

Bob

PS. A reddit thread on 400G

@davidBar-On
Copy link
Contributor

Submitted PR #1690 with support for the requested features (see the PR for details).

@davidBar-On
Copy link
Contributor

Enhanced functionality for this issue now implemented by PRs #1717 (SKIP-RX-COPY) and and #1720 (zerocopy using MSG_ZEROCOPY/SO_ZEROCOPY). PR #1690 with the initial suggestions for the implementations is now closed.

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

No branches or pull requests

2 participants