CUfileIOEvents(3)

okay so bestie, welcome to CUfileIOEvents(3) — and yes, this page is from the Library Functions Manual, folded in right here at the top like a little name tag. Let’s go 💅✨

✨ NAME ✨

CUfileIOEvents

Literally just that, bestie. Iconic behavior, no notes. 🎀

---

🌸 SYNOPSIS 🌸

To get this beauty into your code, include the header:

#include <cufile.h>

🎀 Data Fields 🎀

Here’s the field lineup — one bullet each, no cap:

• void * cookie
• size_t ret
• CUfileStatus_t status

---

🔥 Field Documentation 🔥

🌟 void* CUfileIOEvents::cookie 🌟

This is the cookie field on CUfileIOEvents. The Data Fields list shows it as void * cookie, and the field documentation heading is void* CUfileIOEvents::cookie. That’s the whole note — short and slay. 🍓

💫 size_t CUfileIOEvents::ret 💫

This is the ret field on CUfileIOEvents, typed size_t. The Data Fields list shows it as size_t ret, and the field documentation heading is size_t CUfileIOEvents::ret. Clean, simple, done. 🦋

🦋 CUfileStatus_t CUfileIOEvents::status 🦋

This is the status field on CUfileIOEvents, typed CUfileStatus_t. The Data Fields list shows it as CUfileStatus_t status, and the field documentation heading is CUfileStatus_t CUfileIOEvents::status. Periodt. 💜

---

👑 AUTHOR 👑

Generated automatically by Doxygen for GPUDirect Storage from the source code. Slay, automated author. 🤖💖

---

Bye bestie 🫶 — source/version: GPUDirect Storage, date: Wed Mar 13 2024. Mwah 💋