sunrpc_cache...sts_snapshot(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… sunrpc_cache_requests_snapshot(9) πŸ’…

okay bestie, welcome to the Kernel API Manual, section 9 β€” this one's all about grabbing a lil snapshot of the upcall requests that are still pending ✨


🌸 NAME 🌸

sunrpc_cache_requests_snapshot β€” literally just snapshot pending upcall requests. that's the whole vibe 🫢


πŸŽ€ SYNOPSIS πŸŽ€

int sunrpc_cache_requests_snapshot (struct cache_detail *cd , struct cache_head **items , u64 *seqnos , int max , u64 min_seqno );

πŸ’– ARGUMENTS πŸ’–

  • cd β€” the cache_detail you're querying. this is the main character of the operation πŸ‘‘
  • items β€” an array you (yes, you, the caller) allocated, and it gets filled up with cache_head pointers 🧚
  • seqnos β€” another caller-allocated array, this one gets the sequence numbers dropped into it πŸŽ€
  • max β€” the size of those arrays. don't overfill, bestie, that's the whole point of this number πŸ’€
  • min_seqno β€” only entries with seqno > min_seqno get included. pass 0 and you get everything 🌈

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea πŸ“ only entries that have CACHE_PENDING set make it into the snapshot. no pending, no entry, periodt.

for each one it takes a reference on the cache_head via cache_get β€” so like, it's holding onto them for you πŸ’… which means you gotta call cache_put on every single returned item when you're done with it. every one. don't leave them hanging 😭

fr fr, remember the cache_put. that's not optional, that's the rules 🫢

it returns the number of entries filled. that's it, that's the count 🌟


⭐ SEE ALSO ⭐


and that's the page, bestie!! πŸŽ‰ brought to you straight out of ./net/sunrpc, dated October 2026 β€” same iconic header, same iconic footer, just with way more sparkle βœ¨πŸ’œ slay, go snapshot some requests πŸ”₯

πŸ“¦ where this page comes from