GFS_PIO_FLUSH(3)

πŸ’– GFS_PIO_FLUSH(3) πŸ’–

okay bestie, welcome to the Gfarm section 3 manual, and today's main character is gfs_pio_flush β€” the little function that makes sure your data actually leaves the building. no cap. ✨


🌸 NAME 🌸

gfs_pio_flush β€” flush a stream 🚿


πŸŽ€ SYNOPSIS πŸŽ€

#include <gfarm/gfarm.h>

gfarm_error_t gfs_pio_flush(GFS_File gf);

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea: gfs_pio_flush() forces a write of all user-space buffered data for the given output gf. like, everything that was just chillin' in the buffer? it's going out. now. not later, not when the buffer feels like it β€” right now. it's giving "we're leaving, grab your coat" energy. πŸ’…

(also note it says output gf β€” this is a write-flush situation, iykyk.)


✨ RETURN VALUES ✨

  • GFARM_ERR_NO_ERROR β€” slay πŸ’… the function terminated successfully. everything worked, no notes, iconic behavior.
  • GFARM_ERR_NO_MEMORY β€” 😭 insufficient memory was available. the vibe check failed, there was simply not enough room.
  • Others β€” some other error happened that isn't either of the two above πŸ™ˆ. the reason gets shown to you by gfarm_error_string(3), so go read that to find out what went wrong, bestie.

πŸ‘‘ SEE ALSO πŸ‘‘


and that's the whole page, bestie β€” this was Gfarm, dated 20 Jun 2019, signing off with a little sparkle ✨🫢 go forth and flush responsibly πŸ’–