get_max_segment_size(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… get_max_segment_size β€” kernel API manual (section 9, bestie)

okay so welcome to the get_max_segment_size(9) page, straight out of the Kernel API Manual ✨ this is the one that tells you the maximum number of bytes you can add as a single segment. yes, that's the whole vibe. let's get into it 🫢


✨ NAME ✨

get_max_segment_size β€” maximum number of bytes to add as a single segment πŸ‘‘


🌸 SYNOPSIS 🌸

unsigned get_max_segment_size (const struct queue_limits *lim ,
phys_addr_t paddr , unsigned int len );

like, look at her. three args, returns an unsigned, main character energy fr fr πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • lim β€” Request queue limits. the literal limits of the request queue, she's the rulebook πŸ“‹
  • paddr β€” address of the range to add πŸ“
  • len β€” maximum length available to add at paddr. key word maximum, don't forget it πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

Returns the maximum number of bytes of the range starting at paddr that can be added to a single segment. that's it, that's the function. she's short, she's sweet, she knows exactly what she's about βœ¨πŸ’–


πŸ’œ SEE ALSO πŸ’œ

iykyk, go read those next 🌈


no cap bestie, this is the whole page β€” every arg, every type, all of it, nothing skipped πŸ’€

okay and for the cute lil sign-off: this one lives under ./block, dated October 2026, and it's get_max_segment_size(9) all over again in the footer. slay, periodt πŸŽ€πŸ¦‹πŸ’…

πŸ“¦ where this page comes from