Kitchen sink test post

This is a normal paragraph. It has bold text, italic text, and inline code scattered through it. Here is a link to somewhere and another link with a longer label.

Headings

H3 looks like this

H4 if we have one

Lists

Unordered:

• First item
• Second item with a bit more text in it so we can see wrapping behaviour
• Third item

Ordered:

1. Step one
2. Step two
3. Step three

Code blocks

A short one:

echo "hello world"

A longer one that should scroll horizontally:

func (s *Server) handlePacket(conn *net.UDPConn, buf []byte, n int, addr *net.UDPAddr) error {
    msg := strings.TrimSpace(string(buf[:n]))
    parts := strings.SplitN(msg, " ", 6)
    if len(parts) < 6 {
        return fmt.Errorf("malformed packet from %s: %q", addr, msg)
    }
    return s.dispatch(parts[0], parts[1], parts[2], parts[3], parts[4], parts[5])
}

A multi-language one:

import socket

sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
sock.bind(("0.0.0.0", 9000))

while True:
    data, addr = sock.recvfrom(4096)
    print(f"received {len(data)} bytes from {addr}")

Blockquote

The network is the computer. Or at least, the network is where everything interesting happens once you stop writing CRUD apps.

Horizontal rule

A longer paragraph

Kernel bypass is one of those topics that sounds arcane until you realise the entire premise is just: the OS kernel adds latency, so skip it. DPDK, AF_XDP, io_uring — they’re all different answers to the same question. At some point the abstraction costs more than it gives you and you end up writing C again like it’s 1994.