cppvalleyC++ · Systems · Low Latency · HFT
HFT Core Systems

HFT CORE SYSTEMS

System calls and context switches are different things

Lesson 28 of 96Phase 03: Linux determinism
Video lesson coming soon

The written objectives and hands-on lab are available now.

cppvalley on YouTube ↗

Learning objectives

What you should understand

  1. Separate privilege transitions from scheduler switches
  2. Measure syscall cost without folklore
  3. Identify blocking paths that actually deschedule

Lab

Hands-on exercise

Compare a nonblocking syscall, a blocking call and an intentional yield.

Deliverable

Evidence of completion

A measured taxonomy of calls, switches and their observation points.

Prerequisite
EP 27

Phase 03

Linux determinism

Full curriculum
21Scheduler classes and real-time hazards22Affinity, topology, SMT, and migration23CPU isolation as a system configuration24Interrupts, NAPI, softirqs, and NIC queues25Memory locking and prefaulting26Power management, turbo, C-states, and thermal behavior27Finding OS noise with rtla, ftrace, and perf28System calls and context switches are different things29Shared memory IPC with explicit ownership30cgroup v2, cpusets, memory nodes, and least privilege31Asynchronous logging: page cache, direct I/O, and io_uring32Phase gate: reproducible low-jitter host profile