You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should there be a higher granularity for selecting devices? For example, for cases where one wants to select a high-VRAM device (e.g. for machine learning workloads) or the non-dominant (e.g. secondary device which hopefully will not jank the current compositor) device. Allowing a single application to be the dominant resource user is not new, but it is definitely something that want to be careful about.
The text was updated successfully, but these errors were encountered:
kdashg
changed the title
[from TAG] Should there be a higher granularity for selecting devices?
[TAG review] Should there be a higher granularity for selecting devices?
May 25, 2022
Resolved today: this isn't necessary because almost all machines have either 1 or 2 devices which are already addressable by just the high-performance/low-power existing toggle.
We moved it to post-V1 instead of closing it because there's a possibility that devs will come to us with this requirement in the future. However, I think we should just close it, because there's not much discussion on this issue and I'm sure it would end up getting filed as a new one anyway. (Or we can reopen this when the time comes.)
From w3ctag/design-reviews#626 (comment)
The text was updated successfully, but these errors were encountered: