ENUM RNBD_MSG_TYPE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum rnbd_msg_type(9) β€” like, the RNBD message types bestie

okay so this is a page from the Kernel API Manual, and honestly? it's giving "short but iconic." no cap, every single constant matters here, so let's get into it 🫢


✨ NAME ✨

enum rnbd_msg_type β€” the RNBD message types. that's it, that's the vibe. these are the message kinds floating around in RNBD land πŸ’Œ


πŸ¦‹ SYNOPSIS πŸ¦‹

here's the whole enum, and yes you're gonna read all of it, it's not that long bestie:

enum rnbd_msg_type {
    RNBD_MSG_SESS_INFO ,
    RNBD_MSG_SESS_INFO_RSP ,
    RNBD_MSG_OPEN ,
    RNBD_MSG_OPEN_RSP ,
    RNBD_MSG_IO ,
    RNBD_MSG_CLOSE

};

🌸 Constants 🌸

okay so these are the actual constants, and each one is literally serving a purpose:

  • RNBD_MSG_SESS_INFO β€” the initial session info, going from client ➑️ server. first impressions, main character energy ✨
  • RNBD_MSG_SESS_INFO_RSP β€” the initial session info, but coming back from server ➑️ client. it's the reply, and it ate πŸ’…
  • RNBD_MSG_OPEN β€” the open (map) device request. asking to be let in, very demure πŸ™ˆ
  • RNBD_MSG_OPEN_RSP β€” the response to an RNBD_MSG_OPEN. so like, the answer to the ask πŸŽ€
  • RNBD_MSG_IO β€” block IO request operation. the actual getting-things-done one, highkey the busy icon of the group πŸ”₯
  • RNBD_MSG_CLOSE β€” the close (unmap) device request. saying goodbye, and we respect it 😭

πŸ‘‘ SEE ALSO πŸ‘‘

  • Kernel file ./drivers/block/rnbd/rnbd-proto.h
  • struct rnbd_msg_hdr(9)
  • struct rnbd_msg_sess_info(9)
  • struct rnbd_msg_sess_info_rsp(9)
  • struct rnbd_msg_open(9)
  • struct rnbd_msg_close(9)
  • struct rnbd_msg_open_rsp(9)
  • struct rnbd_msg_io(9)
  • enum rnbd_io_flags(9)

like, go read all of those too, they're all in ./drivers/block/rnbd/rnbd-proto.h and they're all connected, iykyk 🌈


and that's the whole page bestie!! this one came from ./drivers/block/rnbd and it's dated October 2026 β€” periodt, go forth and reference your message types responsibly πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from