nfs_coalesce_size(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nfs_coalesce_size(9) πŸ’…

ok so this is a kernel API manual page, bestie β€” it lives in the Kernel API Manual section and honestly it's giving "small function, big responsibilities" energy. Let's get into it ✨


🌸 NAME 🌸

nfs_coalesce_size β€” the vibe check that tells you whether two requests are compatible enough to smoosh together 🫢


✨ SYNOPSIS ✨

unsigned int nfs_coalesce_size (struct nfs_page *prev , struct nfs_page
*req , struct nfs_pageio_descriptor *pgio );

πŸŽ€ ARGUMENTS πŸŽ€

  • prev β€” pointer to nfs_page (the one that came first, the og request πŸ’…)
  • req β€” pointer to nfs_page (the new one trying to get in on the action)
  • pgio β€” pointer to nfs_pagio_descriptor (yes that's how it's spelled here, don't come for me, I'm just the messenger 😭)

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so real talk: the nfs_page structures prev and req get compared. what are we comparing, you ask? we're making sure that:

  • the page data area they describe is contiguous β€” like, actually next to each other, no gaps, no awkwardness πŸ‘‘
  • their RPC credentials are the same
  • their NFSv4 open state is the same
  • their lockowners are the same

if all of that lines up? slay. they're compatible.

Returns the size of the request that can be coalesced. periodt. πŸ’–


🌈 SEE ALSO 🌈

kernel file ./fs/nfs/pagelist.c β€” that's where the magic lives, iykyk 🧚

and the whole friend group, fr fr:


ngl, "coalesce" is such a main character word. it's giving "come together, become one, ate" πŸ”₯

ok that's the page!! sourced straight from ./fs/nfs, dated October 2026, and it's the nfs_coalesce_size(9) manual page signing off β€” stay contiguous, stay credential-consistent, and don't let anyone tell you your lockowner is different πŸ’œπŸŽ€βœ¨

πŸ“¦ where this page comes from