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

Image init data buffer #719

Open
rjodinchr opened this issue Aug 30, 2024 · 1 comment · May be fixed by #720
Open

Image init data buffer #719

rjodinchr opened this issue Aug 30, 2024 · 1 comment · May be fixed by #720

Comments

@rjodinchr
Copy link
Contributor

At the moment clvk defers the initialisation of image content given at creation (either by CL_MEM_COPY_HOST_PTR or CL_MEM_USE_HOST_PTR).

It leads to a staging buffer being allocated until the data is actually copied to the image memory.

I have an application where lots of images with init data are created and it ends up hitting an out-of-memory.

Could we have a mode where the copy of the data to the image memory is done at creation time, not at first use?
@rjodinchr
Copy link
Contributor Author

The issue with doing it at creation time seems to be the lack of clCommandQueue.

But maybe we can do without it and just do something as we already have VkQueue

rjodinchr added a commit to rjodinchr/clvk that referenced this issue Sep 2, 2024
@rjodinchr
init image at creation time
69ed7b5 
fix kpet#719
@rjodinchr rjodinchr linked a pull request Sep 2, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

init image at creation time rjodinchr/clvk
1 participant
@rjodinchr