| commit | 72d742324adbf59cafa15ef03fd9e4719307aecb | [log] [tgz] |
|---|---|---|
| author | Sean Klein <smklein@google.com> | Sun Apr 22 21:32:57 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jun 12 23:51:37 2018 +0000 |
| tree | 887f9563c6e0ea8ec29db837e41b6af348e0d3c5 | |
| parent | 903a82823d578049e69b67ab8b1725ae244830ae [diff] |
[blobfs] Implement optional blobfs compression Consider compression during writeback, and only write to disk in compressed format if a minimal number of blocks would be saved. Overview: - Compression utilities are implemented in lz4.h / lz4.cpp. - Compression is aborted partway through writeback if not enough storage would be saved, avoiding the overhead of needless compression. - Storage space for compressed buffer is released immediately when the blob write has completed. - Decompression happens up front in "InitVmos". - Since writeback may be delayed, paginate it for large buffers to avoid overflowing the writeback buffer. Add tests for this condition in both the compressed and uncompressed cases. ZX-2035 #done Change-Id: I231190bde0939094e932aa1eb28281e3811aca56
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.