ENUM QUEUE_TYPE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ NAME πŸ¦‹

ok so this is enum queue_type(9) β€” the kernel API manual page for enum queue_type, which is literally just… the type of a queue πŸ’… that's it, that's the whole vibe. it's the little enum that tells you who writes to a queue and who reads from it, iykyk.


✨ SYNOPSIS ✨

bestie, here's the whole thing, no notes:

enum queue_type {
    QUEUE_TYPE_TO_CLIENT ,
    QUEUE_TYPE_FROM_CLIENT ,
    QUEUE_TYPE_FROM_ULP ,
    QUEUE_TYPE_TO_ULP

};

πŸŽ€ Constants πŸŽ€

okay so these are the four members, and each one is basically a "who's allowed to touch this queue" vibe check πŸ”₯

  • QUEUE_TYPE_TO_CLIENT β€” so this queue is written by the rxe driver and read by the client, and that client might be a user space application or a kernel ulp. heads up though: this one is used by rxe internals only πŸ™ˆ
  • QUEUE_TYPE_FROM_CLIENT β€” the flip side, gorgeous πŸ’– the queue is written by the client and read by the rxe driver. also used by rxe internals only, so don't go thinking you can just help yourself ✨
  • QUEUE_TYPE_FROM_ULP β€” this queue is written by the kernel ulp and read by the rxe driver. and this one is used by kernel verbs APIs only on behalf of ulps 🫢
  • QUEUE_TYPE_TO_ULP β€” and finally, the queue is written by the rxe driver and read by the kernel ulp. same deal as above: used by kernel verbs APIs only on behalf of ulps πŸ‘‘

like honestly? four constants, four directions, zero ambiguity. main character energy from every single one of them 🌈


🌈 SEE ALSO 🌈

if you wanna go read the actual source (and honestly, go off πŸ‘‘), it's right here:

  • Kernel file ./drivers/infiniband/sw/rxe/rxe_queue.h πŸ¦‹

and that's the whole page, bestie, no cap πŸ’œ this lil icon dropped from ./drivers/infiniband/sw/rxe back in October 2026 β€” periodt, go read the header file, it ate πŸ’…βœ¨πŸ“

πŸ“¦ where this page comes from