| commit | 276323d93f8a69887e20632b0c67c163706c389d | [log] [tgz] |
|---|---|---|
| author | Tricia Landers <planders@google.com> | Wed Oct 31 14:30:40 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sat Nov 03 00:10:32 2018 +0000 |
| tree | 5a689bd0f5666b3e4f357f6310b66d3b8df05967 | |
| parent | f6345cdaf6d9bd675ad5fdd61211f9c83af370d2 [diff] |
[blobfs] Split blob verification into chunks On VerifyContents, instead of reading the entire blob back before comparing its contents, only verify one 8192 byte chunk at a time. ZX-2939 #done Test: TestLargeBlob on qemu with 2gb memory Change-Id: I8b2250e18c6e23adb9afc441557338adc845c4b5
Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/zircon
The Zircon Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.