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

Investigate removal of on-device image copies #1

Open
felixdoerre opened this issue Sep 8, 2018 · 2 comments
Open

Investigate removal of on-device image copies #1

felixdoerre opened this issue Sep 8, 2018 · 2 comments

Comments

@felixdoerre
Copy link
Owner

Currently primus-vk does a image copy on the rendering gpu and one on the displaying gpu. It needs to be checked if those copies are both principally needed or can be removed somehow.

@nariox
Copy link
Contributor

nariox commented Oct 10, 2019

In the meantime, would implementing a AVX or SSE accelerated memcpy improve performance?

I'm actually not too familiar with how memory copies work between the CPU and GPU.

@felixdoerre
Copy link
Owner Author

I assume we already use sse. On 64-bit automatically and on 32-bit with something like these:
#37 (comment)
It seems I missed adding the 32-bit trick to the generic Makefile.

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