Lines Matching full:cpu

17 LibCEED generally follows a "CPU first" implementation strategy when adding new functionality to th…
18 …ce specific considerations, it is generally recommended to include a basic CPU default implementat…
29 …ple, the `/cpu/self/xsmm/serial` backend implements the `CeedTensorContract` object itself but del…
48 ### CPU Backends
50 The basic CPU with the simplest implementation is `/cpu/self/ref/serial`.
52 Most of the other CPU backends only update the {ref}`CeedOperator` and `CeedTensorContract` objects.
54 The `/cpu/self/ref/blockend` and `/cpu/self/opt/*` backends delegate to the `/cpu/self/ref/serial` …
55 The `/cpu/self/ref/blocked` backend updates the {ref}`CeedOperator` to use an E-vector and Q-vector…
56 The `/cpu/self/opt/*` backends update the {ref}`CeedOperator` to apply the action of the operator i…
59 The `/cpu/self/avx/*` and `/cpu/self/xsmm/*` backends delegate to the corresponding `/cpu/self/opt/…
62 The `/cpu/self/memcheck/*` backends delegate to the `/cpu/self/ref/*` backends.
246 …Note: Prefixing the resource with "help:" (e.g. "help:/cpu/self") will result in @ref CeedInt() pr…
248   @param[in]  resource Resource to use, e.g., "/cpu/self"