Originally posted by coder
View Post
Announcement
Collapse
No announcement yet.
Intel Adds GPU-Accelerated Memory Copy Support To FFmpeg
Collapse
X
-
- Likes 1
-
Originally posted by ms178 View PostMaybe there is a comeback of similar functionality on the AMD side soon,
Leave a comment:
-
Originally posted by syrjala View Post
That's actually just a cache.
Leave a comment:
-
Originally posted by coder View PostContext is everything. The new memcpy replaces an exisiting, userspace, CPU-based one. That should tell you that this is nothing to do with the buffer memory being outside the process' address space.
- Likes 1
Leave a comment:
-
Originally posted by ms178 View Post
Maybe there is a comeback of similar functionality on the AMD side soon, just think of their chiplet approach with HBM on the same package. That implies HSA-like functionality not only on APUs but on their next-gen high performance cores as well.
- Likes 2
Leave a comment:
-
Originally posted by fuzz View PostShame HSA never really caught on :/
Also the industry is now zeroing in on CXL as a cache coherent protocol standard for connecting several devices together. That is also an important ingredient in the overall picture.
- Likes 2
Leave a comment:
-
Guest repliedOriginally posted by coder View PostGiven that system & video memory are the same physical RAM (in the iGPU case - the only one, currently), this only makes sense to me if ffmpeg doesn't know how to manage or use Intel's buffers.
The only argument I can see why it might be strictly necessary to do the copy is that pre-Broadwell iGPUs didn't support shared memory between CPU & GPU. Of course, that's assuming that your app needs access to the output frame before it's displayed on screen. And, what blows a hole in that explanation is that a non-GPU version of the copy exists as a starting point.
Anyway, if you're just going to display it after decoding, then just teach ffmpeg how to manage Intel's buffers and leave the data in "video" memory.
So in the case of an iGPU, or if the decoded data is just going to be displayed, there's no reason to perform copies and move it around.
- Likes 1
Leave a comment:
-
Originally posted by coder View PostWas, but not in Skylake.
https://www.anandtech.com/show/10281...sors-65w-edram
- Likes 2
Leave a comment:
-
Originally posted by microcode View PostIn this case, the copy is needed because ffmpeg wants to do something with it on the CPU, in the ffmpeg process's address space, which typically can't operate directly on the GPU memory.
- Likes 1
Leave a comment:
Leave a comment: