STARPU_TCPIPEXEC(1)

🌸 STARPU_TCPIPEXEC 💅

okay so this is a page from the User Commands section of the manual, and it's all about starpu_tcpipexec, bestie. she runs TCP/IP applications. that's the whole vibe. let's get into it ✨

---

🎀 NAME 🎀

starpu_tcpipexec — execute a TCPIP application, no cap 🫶

---

🌈 DESCRIPTION 🌈

so basically, this thing executes a StarPU TCP IP application. that's it, that's the whole job. main character energy fr fr 💖

the way you call her is like this:

./starpu_tcpipexec [option ....] application

yes, that's literally four dots in [option ....] — do not come for me, that's what she says 😭

---

✨ OPTIONS ✨

• -np — here's where you set the number of workers 👑
• -nobind — no description given on this one, she's mysterious and we respect it 🙈
• -ncpus — this one sets how many threads you wanna use on the TCP/IP Slave devices 💅 (and yes, there's an environment variable for this: STARPU_NTCPIPMSTHREADS — write that down ✍️)
• -nolocal — again, no blurb in the source. she simply exists. iconic ⭐
• -ex — use this to specify an external launcher for the application 🔥
• -v — prints the version information and dips out 🦋
• -h — shows the help and exits, your little emergency exit 🚪

---

🧚 EXAMPLES 🧚

here's how the girlies actually run her:

./starpu_tcpipexec -np 2 -nobind -ncpus 1 myapp ./starpu_tcpipexec -np 2
-nobind -ncpus 1 -ex 'xterm -e gdb' myapp

that's 2 workers, -nobind, -ncpus 1 on myapp — and then the same thing again but with -ex 'xterm -e gdb' so the whole thing launches under an external launcher 🍓 so extra, we love her.

---

😭 REPORTING BUGS 😭

found a bug? do not suffer in silence, bestie. report bugs to <starpu-devel@inria.fr> — they wanna hear from you 🫶

---

lowkey reminder: keep every flag exactly as written. -nobind is not --nobind, and STARPU_NTCPIPMSTHREADS is not a vibe you can abbreviate. copy-paste is self care 💜

---

and that's the whole page!! this one's from StarPU 1.4.10, dated September 2026 💖 slay, you read a manpage, periodt ✨👑