UMAD_GET_ISSM_PATH(3)

πŸ“¦
version 65.0 Β· 2 versions
  • 65.0 Β· alpine 3.24, arch rolling, centos-stream 10, centos-stream 9, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.3.10.2 Β· nixos 26.05, nixpkgs unstable
, in alpine 3.24, arch rolling, centos-stream 10, centos-stream 9, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– UMAD_GET_ISSM_PATH(3) πŸ’–

ok so bestie, we're in the OpenIB Programmer's Manual today and the vibe is issm device paths ✨ stay with me, it's literally so simple.


🌸 NAME 🌸

umad_get_issm_path β€” get path of issm device πŸ¦‹


✨ SYNOPSIS ✨

#include <infiniband/umad.h>

int umad_get_issm_path(char *ca_name, int portnum,char*path,intmax);

πŸŽ€ DESCRIPTION πŸŽ€

okay so umad_get_issm_path() resolves the path to the issm device β€” and that's the device you use for setting/clearing the PortInfo:CapMask IsSM bit, iykyk πŸ’… β€” for the portnum of the IB device ca_name.

It stashes that resolved path into the path array, and path cannot exceed max bytes in length (that includes the NULL terminator, bestie, don't forget it 😭).

And here's the tea: opening the issm device sets the PortInfo:CapMask IsSM bit, and closing it clears it. periodt. πŸ‘‘


πŸ”₯ RETURN VALUE πŸ”₯

umad_open_port() returns 0 on success and a negative value on error, like this:

  • -ENODEV β€” the IB device can't be resolved, it's giving nothing to work with πŸ’€
  • -EINVAL β€” the port is not valid (bad portnum or no umad device) πŸ™ˆ

🌈 SEE ALSO 🌈


πŸ‘‘ AUTHOR πŸ‘‘

Sasha Khapyorsky <sashak@voltaire.com> 🫢


OpenIB Β· Oct 18, 2007 β€” that's the whole page bestie, slay, go open that issm device and clear that bit, no cap πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from