time_after32(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay bestie, welcome to time_after32(9) β€” that's the title, and this page is living in the Kernel API Manual. It's literally here to compare two 32-bit relative times, no cap. πŸ’…


✨ SYNOPSIS ✨

time_after32 (a , b );

πŸŽ€ ARGUMENTS πŸŽ€

  • a β€” the time which may be after b πŸ’–
  • b β€” the time which may be before a 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

So time_after32(a, b) returns true if the time a is after time b. And time_before32(b, a) returns true if the time b is before time a. Cute, right? It's similar to time_after, but it compares two 32-bit timestamps for relative times.

This is the move when you're comparing 32-bit seconds values that can't be converted to 64-bit values β€” e.g. because of disk format or wire protocol issues β€” and you know that the times are less than 68 years apart. That's the whole vibe check: keep it 32-bit, keep it relative, and keep it under 68 years apart. ✨


πŸ‘‘ SEE ALSO πŸ‘‘


mwah πŸ’‹ this page is from ./include/linux, dated October 2026, and it's signing off as time_after32(9) β€” periodt. πŸŽ€

πŸ“¦ where this page comes from