sc::MemoryDataRequest(3)

πŸ“¦
version 2.3.1 Β· 4 versions
, in fedora 43, ubuntu noble

πŸ’– NAME πŸ’–

sc::MemoryDataRequest β€” bestie, this is the little request object from MPQC that carries around everything you need to know about a memory data request: which kind of request it is, which node it belongs to, where it starts, how big it is, lock stuff, serial number, all of it. ✨


🌸 SYNOPSIS 🌸

This page lives in the <strong>Library Functions Manual</strong>, and it's giving very much "C++ class documentation, but make it cute." Here's the whole vibe of what sc::MemoryDataRequest is packing:

✨ Public Types ✨

enum { NData = 6 }
enum Request { Deactivate, Sync, Retrieve, Replace, DoubleSum }

πŸ¦‹ Public Member Functions πŸ¦‹

MemoryDataRequest (Request r, int node=0, int offset=0, int size=0, int
    lock=0, int serial=0)
void assign (Request r, int node, int offset, int size, int lock, int
    serial)
void * data () const
int nbytes () const
const char * request_string () const
MemoryDataRequest::Request request () const
int node () const
int offset () const
int size () const
int serial_number () const
int lock () const
int touches_data () const
int reactivate () const
void operator= (const MemoryDataRequest &r)
void print (const char *msg=0, std::ostream &o=ExEnv::out0()) const

Like… look at that list. Every single one of those is here, no cap. We don't skip, we don't summarise, we respect the API. πŸ’…


🫢 Author 🫢

Generated automatically by Doxygen for MPQC from the source code.

Not me being written by a robot and still serving this much cunt. πŸ™ˆ Doxygen did the typing, MPQC did the existing, and honestly? Slay.

And that's the whole page, bestie!! 🌈✨ This was <strong>MPQC, Version 2.3.1</strong>, and the manpage itself is filed as <code>sc::MemoryDataRequest(3)</code>. Go forth and request your memory data responsibly. Periodt. πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from