This website requires JavaScript.
About
Status
₊˚⊹Discord
Explore
Register
Sign in
Reference in a new issue
Blame
Copy permalink
Reference in a new issue
Copy permalink
DKB
/
zml
Star
0
Fork
You've already forked zml
0
mirror of
https://github.com/zml/zml.git
synced
2026-11-16 19:11:09 +00:00
Code
Issues
23
Releases
1
Packages
Activity
steeve/zig_binary
zml
/
examples
/
simple_layer
/
main.zig
99 lines
3.6 KiB
Raw
Permalink
Normal View
History
zml: initial release
2024-09-17 11:11:18 +02:00
WIP
2025-08-14 15:55:29 +02:00
zml: initial release
2024-09-17 11:11:18 +02:00
WIP
2025-08-14 15:55:29 +02:00
zml: initial release
2024-09-17 11:11:18 +02:00
zml: add stdx, rework async signature inference (#89) This one is a chonky. This commit adds a new `stdx` module with a few utility functions. It is very far reaching. Forgive the size. Also, clean the logs in the executables.
2024-11-15 17:12:07 +01:00
zml: initial release
2024-09-17 11:11:18 +02:00
pjrt/zml: expose client creation flags (#129) The Pjrt api allows to passe string flags to the plugin on client creation. Since we don't like working with strings I've converted the strings supported by the cuda plugin into a struct. For now I've focused on the strings corresponding to the allocator settings following #125 More settings are not exposed ATM, will follow up with #132 https://github.com/openxla/xla/blob/3d31c48c719d331d432132b3e0c2c5ce52650675/xla/pjrt/c/pjrt_c_api_gpu_internal.cc#L76-L86 AFAICT the cpu plugin doesn't read flags at all. Neuron doesn't have known flags, TPU requires more investigation. **Breaking change**: `context.autoPlatform()` -> `context.autoPlatform(.{})`
2024-12-11 13:38:04 +01:00
zml: add stdx, rework async signature inference (#89) This one is a chonky. This commit adds a new `stdx` module with a few utility functions. It is very far reaching. Forgive the size. Also, clean the logs in the executables.
2024-11-15 17:12:07 +01:00
zml: initial release
2024-09-17 11:11:18 +02:00
zml: sharding (#26) First rough support for in-process sharding. The goal of sharding is to allow leveraging several GPUs to collaborate to run one big model. Current implementation: * added `platform.sharding()` describing how the set of devices managed by the current process should be used. * added a `_sharding_info` to shape. * A tensor / shape axis can be marked as needing sharding using `.withSharding(.{ .a })` or `.withSharding(.{ 1 })`. * When using `populateModelWeights` tensors with sharded axes, will be populated by sharded buffers. * when generating the MLIR bytecode for a ZML function the **input** arguments, will see their `_sharding_info` converted into `mhlo.sharding` attributes
2024-10-01 21:12:25 +02:00
zml: initial release
2024-09-17 11:11:18 +02:00
zml: sharding (#26) First rough support for in-process sharding. The goal of sharding is to allow leveraging several GPUs to collaborate to run one big model. Current implementation: * added `platform.sharding()` describing how the set of devices managed by the current process should be used. * added a `_sharding_info` to shape. * A tensor / shape axis can be marked as needing sharding using `.withSharding(.{ .a })` or `.withSharding(.{ 1 })`. * When using `populateModelWeights` tensors with sharded axes, will be populated by sharded buffers. * when generating the MLIR bytecode for a ZML function the **input** arguments, will see their `_sharding_info` converted into `mhlo.sharding` attributes
2024-10-01 21:12:25 +02:00
zml: initial release
2024-09-17 11:11:18 +02:00
examples: fixes related to recent async changes (#96) Recent changes to the `async` module reverted `asyncGeneric` to `asyncc` but examples were not updated
2024-11-20 15:34:38 +01:00
zml: initial release
2024-09-17 11:11:18 +02:00
zml: sharding (#26) First rough support for in-process sharding. The goal of sharding is to allow leveraging several GPUs to collaborate to run one big model. Current implementation: * added `platform.sharding()` describing how the set of devices managed by the current process should be used. * added a `_sharding_info` to shape. * A tensor / shape axis can be marked as needing sharding using `.withSharding(.{ .a })` or `.withSharding(.{ 1 })`. * When using `populateModelWeights` tensors with sharded axes, will be populated by sharded buffers. * when generating the MLIR bytecode for a ZML function the **input** arguments, will see their `_sharding_info` converted into `mhlo.sharding` attributes
2024-10-01 21:12:25 +02:00
zml: initial release
2024-09-17 11:11:18 +02:00
async: rework async runtime to use coroutines and cross thread signaling (#100) This mostly reworks the runtime to enable proper cross thread signaling for `callBlocking`. API changes include: - `async_ -> asyncc` - `await_ -> awaitt` - proper type inference for non generic arguments even for generic functions - bump `libxev` - use `epoll` on linux by default (can be comptime overridden through `xev_options.linux_backend` in the root module) Mostly, also, it's pretty fast.
2024-11-22 17:56:22 +01:00
zml: initial release
2024-09-17 11:11:18 +02:00
zml: cleanup module.zig (#115) * compileInternal now works with function not with "module" * BaseExe now allocates all the memory needed to call `pjrtExecute` * `Exe` is the type variant of `BaseExe` and enforce the right Zig arg are passed to `call`. `exe.prepare(model)` don't need to allocate anymore, the allocation happened during compilation. * public entry points like `compile`, `compileModel`, `compileFn` are now at the top of the file * the caching logic has been mostly inlined inside `compileInternal` * `compile`, `compileFn`, `Exe`, `BaseExe` which are the user visible API have been moved to `exe.zig` * `CompilationContext` and all the compilation logic stays in `module.zig`
2024-12-05 17:33:19 +01:00
zml: initial release
2024-09-17 11:11:18 +02:00
zml: sharding (#26) First rough support for in-process sharding. The goal of sharding is to allow leveraging several GPUs to collaborate to run one big model. Current implementation: * added `platform.sharding()` describing how the set of devices managed by the current process should be used. * added a `_sharding_info` to shape. * A tensor / shape axis can be marked as needing sharding using `.withSharding(.{ .a })` or `.withSharding(.{ 1 })`. * When using `populateModelWeights` tensors with sharded axes, will be populated by sharded buffers. * when generating the MLIR bytecode for a ZML function the **input** arguments, will see their `_sharding_info` converted into `mhlo.sharding` attributes
2024-10-01 21:12:25 +02:00
zml/buffer: various improvements (#248) * `Buffer.from` is blocking by default * `Buffer.from` takes options to control the loading This includes awaiting for the buffer or to which memory the buffer is copied
2025-06-06 18:12:49 +02:00
zml: initial release
2024-09-17 11:11:18 +02:00