Lines Matching full:ref

5 …gle user facing API for creating and using the libCEED objects ({ref}`CeedVector`, {ref}`CeedBasis…
6 Different Ceed backends are selected by instantiating a different {ref}`Ceed` object to create the …
24 A Ceed backend is not required to implement all libCeed objects or {ref}`CeedOperator` methods.
27 1. Delegation - Developers may use {c:func}`CeedSetDelegate` to set a general delegate {ref}`Ceed` …
28 …This delegate {ref}`Ceed` will provide the implementation of any libCeed objects that parent backe…
31 2. Object delegation  - Developers may use {c:func}`CeedSetObjectDelegate` to set a delegate {ref}`…
32 …This delegate {ref}`Ceed` will only provide the implementation of that specific libCeed object for…
35 …se {c:func}`CeedSetOperatorFallbackCeed` to set a {ref}`Ceed` object to provide any unimplemented …
36    The parent backend must implement the basic {ref}`CeedOperator` functionality.
37 …Like the delegates above, this fallback {ref}`Ceed` object should be created and set in the backen…
39 …For example, `/gpu/cuda/gen` falls back to `/gpu/cuda/ref` for missing {ref}`CeedOperator` precond…
40 …e parent `/gpu/cuda/gen` {ref}`Ceed` object uses its fallback `/gpu/cuda/ref` {ref}`Ceed` object t…
41 … This clone {ref}`CeedOperator` is then used for the unimplemented preconditioning support methods.
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…
62 The `/cpu/self/memcheck/*` backends delegate to the `/cpu/self/ref/*` backends.
72 The `/gpu/*/ref` backends provide basic functionality.
73 …ref}`CeedElemRestriction` kernels map from the L-vectors to E-vectors, then {ref}`CeedBasis` kerne…
77 The `/gpu/*/shared` backends delegate to the corresponding `/gpu/*/ref` backends.
78 These backends use shared memory to improve performance for the {ref}`CeedBasis` kernels.
79 All other libCEED objects are delegated to `/gpu/*/ref`.
83 These backends write a single comprehensive kernel to apply the action of the {ref}`CeedOperator`, …
86 The `/gpu/*/magma` backends delegate to the corresponding `/gpu/cuda/ref` and `/gpu/hip/ref` backen…
87 …ide better performance for {ref}`CeedBasis` kernels but do not have the improvements from the `/gp…
96 …- L-vectors described by a standard {ref}`CeedElemRestriction` have a layout described by the `off…
98 …- L-vectors described by a strided {ref}`CeedElemRestriction` have a layout described by the `stri…
109 …- When the size of a {ref}`CeedQFunction` field is greater than `1`, data for quadrature point `i`…
111 …- When the {ref}`CeedQFunction` field has `emode` `CEED_EVAL_GRAD`, data for quadrature point `i`,…
121 …TakeArray` on the only memory location that contains valid data, then the {ref}`CeedVector` is lef…
124 Some checks for consistency and data validity with {ref}`CeedVector` array access are performed at …
129 …- {ref}`CeedVector` access to borrowed memory is set with {c:func}`CeedVectorSetArray` with `copy_…
246 …Note: Prefixing the resource with "help:" (e.g. "help:/cpu/self") will result in @ref CeedInt() pr…
253   @ref User