GLOBUS_XIO_ORDERING_DRIVER_IO(3)

💖 NAME 💖

globus_xio_ordering_driver_io — reading and writing, bestie. That's the whole vibe. 📖✍️

---

✨ SYNOPSIS ✨

🦋 Detailed Description 🦋

Okay so. Reading/Writing. That's it, that's the teaser. 😌

---

🌸 THE ACTUAL TEA 🌸

Here's the thing, babes: the ordering driver is not about letting you have multiple globus_xio_register_read() calls outstanding at the same time. Not even a little. And why? Because it's on a mission — it wants to guarantee that you, the user, get your read callbacks in order. 💅

And ngl, there's a legit reason for that rule: there is a known issue with enforcing the order in which read callbacks get delivered when you've got multiple outstanding reads. So yeah. It's a whole thing. 🙈

But bestie, listen — this limitation does not restrict your use of the parallel reads feature that the underlying transport driver provides. You still get to slay. 👑

So how do you get your parallel reads then? Enter:

• GLOBUS_XIO_ORDERING_SET_MAX_READ_COUNT on the attr — use this to specify the number of parallel reads you want. 🌈

The ordering driver will have a maximum of this many reads outstanding to the driver below it on the stack. Then it does the cute little buffering thing: it buffers the data read and delivers it to the user in order. Iconic behavior, honestly. ✨

---

🫶 AND WHAT ABOUT WRITES 🫶

globus_xio_register_write() — does not enforce any restriction. That's it. No rules, no drama, just vibes. 💜

---

👑 Author 👑

Generated automatically by Doxygen for globus_xio from the source code. Not me writing it by hand, bestie — the machines did that part. 🤖🎀

---

And that's the whole page, fr fr. This lil masterpiece comes to you from the globus_xio manual, Version 6.6, dated globus_xio...g_driver_io(3) — mwah, stan, periodt. 💋💖🦋