GRCLI-AFFINITY(1)

📦
version 0.18.0 · 6 versions
, in fedora 44

✨ GRCLI-AFFINITY(1) ✨

okay bestie, so this is a page from the General Commands Manual — it's all about grcli-affinity, and ngl the whole vibe is "which CPU is doing what and which queue lives where." CPU and physical queue affinity, periodt. 💅

It's the little corner of grcli where you tell your control plane threads and your datapath worker threads which CPUs they get to call home, and where you tell each DPDK port RXQ which worker CPU it belongs to. Lowkey iconic, highkey important. 🧚

🌸 SYNOPSIS 🌸

affinity cpus set [control CONTROL] [datapath DATAPATH]
    Change the CPU affinity lists.

affinity cpus show
    Display CPU affinity lists.

affinity qmap set NAME rxq RXQ cpu CPU
    Set DPDK port queue affinity.

affinity qmap show
    Display DPDK port RXQ affinity.

So yeah — two lil families of subcommands: cpus for the CPU lists, and qmap for the DPDK port queue mapping. set to change stuff, show to look at stuff. That's the whole arc, no plot twists. 🦋

💖 OPTIONS 💖

  • CONTROL — the CPUs you're reserving for the control plane threads. Not me gatekeeping CPUs, but like, reserved fr. 🎀
  • DATAPATH — the CPUs reserved for the datapath worker threads, aka the ones doing the actual heavy lifting. main character energy honestly. 🔥
  • NAME — the interface name. Just the name. That's it, that's the option. 👑
  • RXQ — the RX queue ID. 🍓
  • CPU — the worker CPU ID. Which worker CPU, specifically. ⭐

🌈 SEE ALSO 🌈

go read those too, iykyk. 🫶

🐛 REPORTING BUGS 🐛

found something cursed? 💀 report bugs to the grout project issue tracker at:

https://github.com/DPDK/grout/issues

don't suffer in silence bestie, tell the maintainers. 🙈

psst — this whole thing comes from the General Commands Manual, dated 2026-10-01. manifesting bug-free affinity for u always 💜✨ xoxo, ur resident unix girlie 🎀
📦 where this page comes from