memset64(9)
πΈ MEMSET64(9) β the kernel API manual, but make it cute πΈ
okay so bestie, welcome to the memset64(9) page from the Kernel API Manual π strap in, it's short but it's iconic.
β¨ NAME β¨
memset64 β fill a memory area with a uint64_t π«Ά
π SYNOPSIS π
void * memset64 (uint64_t *s , uint64_t v , size_t count );
that's it. that's the whole vibe. π
π ARGUMENTS π
sβ pointer to the start of the area. like, where the party begins β¨vβ the value you're filling the area with. the whole personality of the bytes, basically πcountβ the number of values to store. and bestie, read the next section before you get cute with this one π
π DESCRIPTION π
so here's the tea: this differs from memset in that it fills with a uint64_t instead of a byte. big chunky values, no cap. π₯
β οΈ remember thatcountis the number ofuint64_tsto store, not the number of bytes. not me warning you twice but like... do not mess this up fr fr π
π¦ SEE ALSO π¦
kernel file ./lib/string.c β and honestly the whole friend group showed up:
strncasecmp(9), stpcpy(9), strcmp(9), strncmp(9), strchr(9), strchrnul(9), strnchrnul(9), strrchr(9), strnchr(9), strspn(9), strcspn(9), strpbrk(9), strsep(9), memset(9), memset16(9), memset32(9), memcpy(9), memmove(9), memcmp(9), bcmp(9), memscan(9), strstr(9), strnstr(9), memchr(9), memchr_inv(9)
like a full group chat, honestly. iykyk π
and that's the page, bestie π§ this little gem lives in ./lib and it's dated October 2026 β so go forth, fill those uint64_ts, and remember: count is not bytes. mwah πππΈ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms