Skip to content

The choice npu in the component object is too narrow #11

@ajbalogh

Description

@ajbalogh

Describe the bug
XPU is the common used term these days to signify gpu/tpu/npu/custom asics etc whereas NPU signifies a more narrow definiton.
The “X” in XPU is often interpreted as a placeholder for “any” or “cross-domain,” signifying flexibility and extensibility. It isn’t one single chip type, but rather a concept and direction in processor architecture where heterogeneous computing resources are unified or designed to work together.
In the data model the enum of NPU should be changed to XPU.

Expected behavior
All mentions of npu in the model, code and documentation should be replaced with xpu.
This will be a breaking change in backward compatiblity and the minor version number should be bumped.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions