12:27 kode54: nice closed bug tracker
13:15 Venemo: kode54: ??
15:05 Feru: I'm working on a larger Unity game which would like to allocate 12-14 GB of VRAM. I have a 20 GB Radeon 7900 XT. On Linux, I'm using Vulkan. I noticed that RADV is struggling to deal with this, swapping very early, while AMDVLK seems just fine. My understanding is that VRAM spilling is handled in the kernel, so why do the implementations differ so much?
15:07 superkuh: GTT mapping differences?
15:07 superkuh: I know there are massive GTT behavior differences between amdgpu and amdgpu-pro on the same hardware re: this.
15:08 superkuh: (I should say consistent hardware, not the same as your hardware)
15:11 Feru: Is this behavior controlled by userspace?
15:11 Feru: It's really strange that RADV wants to put everything into GTT as soon as ~10 GB are occupied. It causes massive slowdowns across the entire system.
15:14 Feru: I don't think it's a bug, or rather I don't really understand what's going on. I would expect VRAM fills up until almost full before GTT gets used. Since I'm a game developer I figured I ask you directly. Let me know if this is handled by Mesa.
15:34 Remco: Venemo: The suse bugtracker (or at the very least the specific bug that was linked) is not public
15:34 Venemo: Remco: which?
15:34 Remco: [15:18] < tzimmermann> Venemo, i'll do. there's a longer discussion at https://bugzilla.suse.com/show_bug.cgi?id=1245531 on the issue.
15:34 Venemo: ah that yeah I didn't look at it
23:06 kode54: Venemo: that suse bugtracker tells me I need to log in with access to view that bug report
23:06 kode54: oh
23:06 kode54: I missed the last 3 lines, hah