Explore >> Select a destination
|
You are here 
|
0x434b.dev | ||
| | | | |
mazzo.li
|
|
| | | | | Pipes are ubiquitous in Unix --- but how fast can they go on Linux? In this post we'll iteratively improve a simple pipe-writing benchmark from 3.5GiB/s to 65GiB/s, guided by Linux `perf`. | |
| | | | |
chao-tic.github.io
|
|
| | | | | ||
| | | | |
gamozolabs.github.io
|
|
| | | | | I blog about random things security, everything is broken, nothing scales, shared memory models are flawed. | |
| | | | |
danielmangum.com
|
|
| | | This is part of a series on the blog where we explore RISC-V by breaking down real programs and explaining how they work. You can view all posts in this series on the RISC-V Bytes page. So far in this series, we have been looking at the assembly generated when compiling relatively simple programs. At this point, we have seen instructions that perform a wide variety of operations. Let's take another look at our minimal example from the Passing on the Stack post: | ||
