ENUM QUEUE_TYPE(9)
π¦ 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms