plpks_get_ma...geobjectsize(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the plpks_get_ma...geobjectsize(9) page from the Kernel API Manual ✨ this one is all about the maximum object size for newer PLPKS config structures, and it’s lowkey iconic πŸ’…

πŸ’– NAME πŸ’–

plpks_get_maxlargeobjectsize β€” get the maximum object size supported for PLPKS config structure version >= 3 πŸŽ€

✨ SYNOPSIS ✨

u32 plpks_get_maxlargeobjectsize (void );

πŸŽ€ ARGUMENTS πŸŽ€

  • void β€” no arguments, literally none, bestie 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here’s the lore: successful execution of the H_PKS_GET_CONFIG HCALL during initialization reads the maximum object size into the local static maxlargeobjectsize variable for PLPKS config structure version >= 3 🌸

this was introduced starting with PLPKS config structure version 3 to allow for objects of size >= 64K πŸ”₯ so yeah, bigger objects got the green light, no cap 🫢

πŸ”₯ RETURN πŸ”₯

  • if PLPKS config structure version >= 3, then the new maximum object size is returned ✨
  • if not, it’s 0 😌

🌈 SEE ALSO 🌈

Kernel file ./arch/powerpc/platforms/pseries/plpks.c is the home base 🏠 and these sibling functions are all part of the friend group πŸ’–


cute sign-off bestie 🫢 source/version is ./arch/powerpc/platforms/pseries, the date is October 2026, and the page is plpks_get_ma...geobjectsize(9) πŸ’–βœ¨

πŸ“¦ where this page comes from