https://bugs.freedesktop.org/show_bug.cgi?id=109695
--- Comment #8 from Michel Dänzer <mic...@daenzer.net> ---
(In reply to Marek Olšák from comment #7)
> An even better solution would be to have a virtual thread affinity that only
> the application can see and change, which should be silently masked by
> administrative policies not visible to the application.
Mesa doesn't really need explicit thread affinity at all. All it wants is that
certain sets of threads run on the same CPU module; it doesn't care which
particular CPU module that is. What's really needed is an API to express this
affinity between threads, instead of to specific CPU cores.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
