Expand description
Native GPU ownership, shared-device injection and per-client isolation.
This layer contains no JSC values. An embedder can supply its renderer’s
device through GpuHost; a JavaScript client’s destroy() never destroys
that physical device or replaces the embedder’s error/loss callbacks.
Structs§
- Adapter
- Adapter
Options - Client
- One logical JavaScript GPUDevice. Resource brands use this id even when two clients share an identical physical device.
- Context
- The physical device and queue, potentially also owned by GPUI.
- Device
Loss - A loss notification owned by the host rather than by any one JS client.
- GpuError
Constants§
- VIRTUALIZED_
FEATURES - Physical capabilities a shared client may lack: redjs validates every JS path to them against the client’s own features and limits.
Traits§
Functions§
- request_
adapter - scoped
- Runs
operationinside this thread’s own error scopes and returns the first error it raised, instead of recording it on a client. - set_
host - Changes the provider for future requests. Existing adapters/devices retain their original provider’s resources and continue to work.
- shareable_
capabilities - What a physical device needs for JS clients to get every feature and the
immediate-data limit the adapter can expose. Hosts creating a shared device
should request these, on an instance with
InstanceFlags::AUTOMATIC_TIMESTAMP_NORMALIZATION.