Scheduling on Hybrid CPUs| wiki.freebsd.org
it's a blog| norasandler.com
I demonstrate how you can write a simple JIT (Just In Time) compiler for x86 in about 1000 lines of C code.| kuterdinel.com
I’m not talking about skill, knowledge, or convincing a world focused on radical acceleration that optimization is necessary. Performance optimization is hard because it’s fundamentally a brute-force task, and there’s nothing you can do about it. This post is a bit of a rant on my frustrations with code optimization. I’ll also try to give actionable advice, which I hope enchants your experience.| purplesyringa's blog
Why take an interest in assembly language and which to learn?| thechipletter.substack.com
本稿では、タスクの切り替えに伴うレジスタの切り替え処理の内、前編 (7月11日公開: https://valinux.hatenablog.com/entry/20240711) では解説しきれなかった部分について解説します。| VA Linux エンジニアブログ
本稿では、旧版1章で解説されていた「プロセススケジューリング」の内、プロセスディスパッチャ(タスクの切り替え処理)について、カーネルv6.8/x86_64のコードをベースに解説します。| VA Linux エンジニアブログ
The first implementation heavy article covering the details of x86 paging, MTRR configuration, VPID/PCID, and initializing an EPT hierarchy.| Reverse Engineering
Introduction Link to heading Good weather is specific weather. Conclusion: there is no such thing as good weather. Pilot’s proverb TLDR: The very same machine code, placed at different addresses, can exhibit drastically different performance. As software developers, we often assume that the performance of a specific piece of code is determined solely by the code itself and the hardware it runs on. This assumption gives us a sense of control when optimizing code for better performance.| www.bazhenov.me
The Redox official website| www.redox-os.org