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

Allow receiver to designate a memory region for incoming objects #122

Open
KenBirman opened this issue Mar 25, 2019 · 0 comments
Open

Allow receiver to designate a memory region for incoming objects #122

KenBirman opened this issue Mar 25, 2019 · 0 comments

Comments

@KenBirman
Copy link
Contributor

In issue #99, we already are proposing to allow the sender to preallocate a memory buffer from Derecho's pinned, mapped memory area and use that as the basis for a p2p_send or ordered_send, with no copying required.

This proposal is similar, but for the receiver side: a receiver that always receives, say, video objects, might want to preallocate a place for the incoming video transfer, and have Derecho put the incoming data directly into that location. This is a separate issue because, due to the way that RDMC chunks large objects, it will be harder to implement the solution (the first chunk always comes into Derecho memory, so the proposed mechanism would still require a memcpy to put that first chunk into its final location). Not enormously harder, but non-trivial.

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

2 participants