sha256_finup...is_optimized(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… sha256_finup_2x_is_optimized β€” a.k.a. the Kernel API Manual page you didn't know you needed πŸŽ€

okay so bestie, welcome to section 9 of the funny little kernel manual, where we answer the question: is this thing actually doing the fast thing, or is it quietly doing the slow thing? πŸ‘€


✨ NAME ✨

sha256_finup_2x_is_optimized β€” checks whether sha256_finup_2x() is running a real interleaved implementation, as opposed to a sequential fallback. no cap, that's the whole gig 🫢


🌸 SYNOPSIS 🌸

bool sha256_finup_2x_is_optimized (void );

it takes nothing, it returns a bool, it's giving lowkey iconic minimalism πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • void β€” literally no arguments. none. zero. the void is voiding πŸ•³οΈβœ¨

⭐ RETURN ⭐

  • true β€” if optimized πŸ’–
  • (and, iykyk, anything that isn't true means you got the other thing πŸ™ˆ)

🌈 CONTEXT 🌈

Any context. fr fr, any context β€” she's flexible like that 🧚


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./include/crypto/sha2.h β€” and honestly the whole sha2 extended universe is here, so buckle up buttercup, we're listing every single one πŸ‘‘

like yes, that's a lot of friends, but they're all family at this point πŸ“


heads up bestie: this page only tells you whether you're optimized β€” it does not promise anything about how the check is done internally, so don't go writing a whole essay about it, mwah πŸ’‹

and that's the vibe check, periodt πŸ’œ this lil cutie came out of ./include/crypto, October 2026 edition β€” go forth and check your optimization status, main character πŸŽ€πŸ«Άβœ¨

πŸ“¦ where this page comes from