iwpm_get_remote_info(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– iwpm_get_remote_info(9) β€” Kernel API Manual πŸ’–

okay bestie, welcome to the Kernel API Manual page for iwpm_get_remote_info β€” this one is literally about getting the remote connecting peer address info, and it's giving kernel-netlink main character energy. ✨

✨ NAME ✨

iwpm_get_remote_info β€” Get the remote connecting peer address info. 🫢 no cap.

πŸ“œ SYNOPSIS πŸ“œ

int iwpm_get_remote_info (struct sockaddr_storage *mapped_loc_addr ,
struct sockaddr_storage *mapped_rem_addr , struct sockaddr_storage
*remote_addr , u8 nl_client );

πŸŽ€ ARGUMENTS πŸŽ€

  • mapped_loc_addr β€” the mapped local address of the listening peer, iykyk.
  • mapped_rem_addr β€” the mapped remote address of the connecting peer. πŸ’…
  • remote_addr β€” the place to store the remote address of the connecting peer. iconic output behavior, fr fr.
  • nl_client β€” the index of the netlink client. that's the vibe check for which client we're talking about. πŸ¦‹

πŸ’« DESCRIPTION πŸ’«

The remote address info is retrieved and provided to the client in remote_addr. πŸŽ€ After that, it is removed from the hash table. periodt β€” that's the whole flow.

πŸ”— SEE ALSO πŸ”—

Kernel file ./drivers/infiniband/core/iwpm_util.c β€” the source file, bestie. And the squad is iwpm_init(9), iwpm_exit(9), iwpm_create_mapinfo(9), iwpm_remove_mapinfo(9). go read those too, they're lowkey part of the lore. 🌸


okay that's the whole page, bestie! 🫢 This one lives in the Kernel API Manual, source path ./drivers/infiniband/core, and the date on the footer is October 2026 β€” iwpm_get_remote_info(9) out. πŸ’…βœ¨

πŸ“¦ where this page comes from