nfsd_nl_ser...s_get_dumpit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nfsd_nl_server_stats_get_dumpit(9) β€” Kernel API Manual πŸŽ€

okay bestie, this is a page from the Kernel API Manual (section 9), and the star of the show is nfsd_nl_server_stats_get_dumpit β€” the function that dumps NFS server statistics. it's giving "kernel internals but make it cute". let's get into it πŸ’–


✨ NAME ✨

nfsd_nl_server_stats_get_dumpit β€” dump NFS server statistics πŸ“Š


🌸 SYNOPSIS 🌸

int nfsd_nl_server_stats_get_dumpit (struct sk_buff *skb , struct
       netlink_callback *cb );

literally that's the whole signature. short, sweet, slays. 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • skb β€” the reply buffer πŸ’Œ like, this is where the answer goes, bestie.
  • cb β€” netlink metadata and command arguments πŸ—‚οΈ the whole context bundle, no cap.

πŸ‘‘ DESCRIPTION πŸ‘‘

okay so the server-stats object gets emitted across one or more netlink messages. it's not always a one-and-done situation β€” it's giving "multi-part story arc" ✨

here's the tracking situation, and it's honestly iconic:

  • cb->args[0] tracks the current section πŸ“
  • cb->args[1] tracks the entry index within that section πŸ”’

so if a section does not fit in the current message, it just gets resumed in the next one. no drama, no lost data, just a little continue-where-we-left-off moment. periodt. πŸ’…

the scalar counters are small, so they get emitted once, in the first message. and then userspace merges the attributes from every message. teamwork makes the dream work fr fr 🫢🌈

Returns the size of the reply, or a negative errno 😭 (yes, the classic "size or sadness" return value, iykyk).


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./fs/nfsd/nfsctl.c and like, this whole friend group of functions πŸ‘―β€β™€οΈ:


πŸŒΈπŸ’– and that's the page, bestie! this one came from the source path ./fs/nfsd, dated October 2026, and it's part of the Kernel API Manual β€” go forth and dump those stats, you absolute main character πŸ‘‘βœ¨πŸ’…

πŸ“¦ where this page comes from