hwloc_obj_...dev_attr_s(3)

πŸ¦‹ NAME πŸ¦‹

hwloc_obj_attr_u::hwloc_osdev_attr_s β€” ok so real talk, this is a page from the Library Functions Manual for Hardware Locality (hwloc), and it's the struct that holds all the OS-device-specific attributes. Bestie, it's giving "one field but she's important" energy πŸ’…


✨ SYNOPSIS ✨

Lowkey the whole entry point is just this include, no cap:

#include <hwloc.h>

πŸŽ€ Data Fields

  • hwloc_obj_osdev_type_t type β€” the one and only field, iykyk. It's the type of the OS device, and yes she has her own dedicated section further down because she's the main character 🌟

πŸ’– Detailed Description πŸ’–

So what is this thing? It's the OS Device specific Object Attributes struct. That's literally the whole vibe β€” it hangs out inside the hwloc_obj_attr_u union and carries the attributes that only make sense for an OS device. Short, sweet, iconic. Periodt. 🫢


πŸ”₯ Field Documentation πŸ”₯

πŸ’œ hwloc_obj_osdev_type_t hwloc_obj_attr_u::hwloc_osdev_attr_s::type

This is the fully-qualified name of the field, spelled out character for character: hwloc_obj_osdev_type_t is her type, hwloc_obj_attr_u is the union she lives in, hwloc_osdev_attr_s is the struct, and type is the member itself. Full government name, no nicknames πŸ’€


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for Hardware Locality (hwloc) from the source code. Not me writing fanfic β€” the robot did it πŸ™ˆ


Fr fr, don't @ me about missing options β€” this page genuinely just has the one field. That's the whole lore. πŸ“

Hardware Locality (hwloc) Β· Version 2.15.0 Β· hwloc_obj_...dev_attr_s(3) β€” mwah, that's a wrap, go read your structs bestie πŸ’–βœ¨πŸŽ€πŸ¦‹πŸ’…

πŸ“¦ where this page comes from