What is the difference between pthread_key_t and C11 _Thread_local?

A strong answer

A strong candidate frames What is the difference between pthread_key_t and C11 _Thread_local? around the exact memory layout, compiler semantics, and hardware execution model covered in Thread-Specific Data and Thread-Local Storage. Explain pthread_keys with destructor callbacks versus _Thread_local automatic per-thread storage duration.

Global and static variables are shared across all threads in a process. While this makes data sharing effortless, it introduces a dilemma when independent threads need their own private contextual state.

Consider three common systems programming scenarios:

1. The errno Variable: When read() fails on Thread 1 and sets errno = EBADF, Thread 2 executing a successful write() must not overwrite Thread 1's error code before Thread 1 inspects it.
2. Per-Thread Pseudo-Random Generators: Calling rand() across multiple threads causes a data race on the internal seed, or serializes all threads behind a global lock.
3. Request and Transaction Contexts: A web server servicing hundreds of concurrent HTTP requests needs to track the active user ID, client IP, or database transaction handle within deep helper functions.

In a production interview, always connect the specification rule to its concrete runtime consequence: state what lives on the stack versus the heap or static storage segment, how the compiler or operating system validates alignments, lifetimes, and error codes, and what happens under adversarial or boundary inputs (such as zero-length buffers, integer overflow, concurrent mutation, or partial I/O). Backing your explanation with a small trace of register/memory state transitions immediately separates senior systems engineers from candidates who only memorized syntax.

What the interviewer is listening for

• Mastery of core invariant: Eliminate global mutex contention by binding private state to threads using pthread keys.
• Mastery of core invariant: Automate dynamic resource reclamation using pthread_key_create destructor callbacks.
• Mastery of core invariant: Implement high-performance zero-overhead storage using C11 _Thread_local and compiler TLS.
• Hardware and ABI awareness: Explaining how sizes, alignments, calling conventions, or kernel boundaries behave on real 64-bit targets rather than relying on implementation-defined assumptions.
• Defensive engineering: Naming the exact compiler flags (-Wall -Wextra -Werror), static analyzers, or runtime sanitizers (-fsanitize=address,undefined,thread) that verify correctness in CI.

Common mistakes

• Explaining only surface syntax without tracing the underlying memory addresses, ownership lifetime, or kernel/user-space state transitions.
• Assuming undefined behavior (such as signed overflow, uninitialized reads, strict-aliasing violations, or dangling pointers) will "just work" because it passed an unoptimized -O0 debug build.
• Ignoring return codes, partial reads/writes, alignment padding, or cleanup paths when an allocation or syscall fails midway through a function.