Repository navigation
WebNN/WebGPU zero-copy device selection #941
Description
Activity
What do you think about remove the
createContext(GPUDevice)function and replacing it with your proposedinteropDeviceoption? This would allow for the case where a non-GPU device is selected based on the preferences but still with a bias towards the best possible interop with WebGPU.Reacted by Zoltan Kis and Ningxin Hu@reillyeon I agree. I think
interopDeviceis a cleaner abstraction than a dedicatedcreateContext(GPUDevice)overload.Reacted by Ningxin Hu- changed the title
[-]WebNN/WebGPU device selection for interop[/-][+]WebNN/WebGPU zero-copy device selection[/+]on Sep 10, 2026 Looks good to me @bbernhar 👍
Reacted by Bryan B
WebNN and WebGPU select devices independently, so zero-copy interop is not guaranteed. Web developers need a reliable way to determine whether a WebNN context and
GPUDeviceare compatible for zero-copy.The WebNN spec does not define how
createContext()andexportToGPU()interact with device selection when both aGPUDeviceandMLContextOptions(such aspowerPreference) are provided.For example, if an app passes a WebGPU
GPUDevicetocreateContext(), zero-copy is only possible if WebNN selects that same device or a compatible one (for example, an NPU or integrated GPU sharing the same memory). Otherwise,exportToGPU()may require a copy or fail because the selected devices are incompatible.One possible solution would be to add an
{ interopDevice: gpuDevice }option tocreateContext()as a hint for interop compatibility. If provided, WebNN would preferentially select a compatible device, allowingexportToGPU()to remain zero-copy when possible.@reillyeon @RafaelCintron @huningxin @anssiko