Intro
The tinygrad framework has four pieces
- a PyTorch like frontend.
- a scheduler which breaks the compute into kernels.
- a lowering engine which converts ASTs into code that can run on the accelerator.
- an execution engine which can run that code.
There is a good bunch of tutorials by Di Zhu that go over tinygrad internals.
Frontend¤
Everything in Tensor is syntactic sugar around function.py, where the forwards and backwards passes are implemented for the different functions. There's about 25 of them, implemented using about 20 basic ops. Those basic ops go on to construct a graph of:
LazyBuffer
¤
LazyBuffer(
device: str,
st: ShapeTracker,
dtype: DType,
op: Optional[Op] = None,
arg: Any = None,
srcs: Tuple[LazyBuffer, ...] = (),
base: Optional[LazyBuffer] = None,
metadata: Optional[Metadata] = None,
)
Bases: MathTrait
The LazyBuffer
graph specifies the compute in terms of low level tinygrad ops. Not all LazyBuffers will actually become realized. There's two types of LazyBuffers, base and view. base contains compute into a contiguous buffer, and view is a view (specified by a ShapeTracker). Inputs to a base can be either base or view, inputs to a view can only be a single base.
Scheduling¤
The scheduler converts the graph of LazyBuffers into a list of ScheduleItem
. One ScheduleItem
is one kernel on the GPU, and the scheduler is responsible for breaking the large compute graph into subgraphs that can fit in a kernel. ast
specifies what compute to run, and bufs
specifies what buffers to run it on.
ScheduleItem
dataclass
¤
Attributes:
Lowering¤
The code in realize lowers ScheduleItem
to ExecItem
with
lower_schedule
¤
lower_schedule(
schedule: List[ScheduleItem],
) -> Generator[ExecItem, None, None]
Source code in tinygrad/engine/realize.py
200 201 202 203 204 205 206 207 208 209 |
|
There's a ton of complexity hidden behind this, see the codegen/
directory.
First we lower the AST to UOps, which is a linear list of the compute to be run. This is where the BEAM search happens.
Then we render the UOps into code with a Renderer
, then we compile the code to binary with a Compiler
.
Execution¤
Creating ExecItem
, which has a run method
ExecItem
dataclass
¤
ExecItem(
prg: Runner,
bufs: List[Optional[Buffer]],
metadata: Optional[Tuple[Metadata, ...]] = None,
)
Methods:
-
run
–
Attributes:
run
¤
run(
_var_vals: Optional[Dict[Variable, int]] = None,
wait=False,
jit=False,
do_update_stats=True,
) -> Optional[float]
Source code in tinygrad/engine/realize.py
166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 |
|
Lists of ExecItem
can be condensed into a single ExecItem with the Graph API (rename to Queue?)
Runtime¤
Runtimes are responsible for device-specific interactions. They handle tasks such as initializing devices, allocating memory, loading/launching programs, and more. You can find more information about the runtimes API on the runtime overview page.
All runtime implementations can be found in the runtime directory.
HCQ Compatible Runtimes¤
HCQ API is a lower-level API for defining runtimes. Interaction with HCQ-compatible devices occurs at a lower level, with commands issued directly to hardware queues. Some examples of such backends are NV and AMD, which are userspace drivers for NVIDIA and AMD devices respectively. You can find more information about the API on HCQ overview page