ext_tree_encode_commit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

ext_tree_encode_commit(9)

okay so welcome to the Kernel API Manual, bestie πŸ’– this page is all about ext_tree_encode_commit, and its whole vibe is β€œencode as much as possible extents into the buffer” ✨


πŸŽ€ NAME πŸŽ€

ext_tree_encode_commit β€” encode as much as possible extents into the buffer.

✨ SYNOPSIS ✨

int ext_tree_encode_commit (struct pnfs_block_layout *bl , __be32 *p ,
size_t buffer_size , size_t *count , __u64 *lastbyte );

🫢 ARGUMENTS 🫢

  • bl β€” pointer to the layout. That’s the layout bestie in question πŸ¦‹
  • p β€” pointer to the output buffer. This is where the encoded extents go πŸ’…
  • buffer_size β€” size of the output buffer. Gotta know how much room we’re working with ✨
  • count β€” output pointer to the number of encoded extents. It reports back how many made it in πŸ”₯
  • lastbyte β€” output pointer to the last written byte. It points at where the writing ended up πŸ‘‘

🌸 DESCRIPTION 🌸

Return values, periodt:

  • 0: Success, all required extents encoded, outputs are valid πŸ’–
  • -ENOSPC: Buffer too small, some extents are encoded, outputs are valid 😭
bestie, notice that in the -ENOSPC case some extents are still encoded and the outputs are still valid β€” the buffer just wasn’t big enough for the whole thing 🫢

🌈 SEE ALSO 🌈


later, babes πŸ’… this page came from ./fs/nfs/blocklayout, dated October 2026 β€” mwah! πŸŽ€

πŸ“¦ where this page comes from