Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   9087 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

PUFFS_CC(3)		 BSD Library Functions Manual		   PUFFS_CC(3)

NAME
     puffs_cc — puffs continuation routines

LIBRARY
     library “libpuffs”

SYNOPSIS
     #include <puffs.h>

     void
     puffs_cc_yield(struct puffs_cc *pcc);

     void
     puffs_cc_continue(struct puffs_cc *pcc);

     void
     puffs_cc_schedule(struct puffs_cc *pcc);

     struct puffs_cc *
     puffs_cc_getcc(struct puffs_usermount *pu);

DESCRIPTION
     These routines are used for the cooperative multitasking suite present in
     puffs.

     puffs_cc_yield(pcc)
	   Suspend and save the current execution context and return control
	   to the previous point.  In practice, from the file system author
	   perspective, control returns back to where either the mainloop or
	   where puffs_dispatch_exec() was called from.

     puffs_cc_continue(pcc)
	   Will suspend current execution and return control to where it was
	   before before calling puffs_cc_yield().  This is rarely called
	   directly but rather through puffs_dispatch_exec().

     puffs_cc_schedule(pcc)
	   Schedule a continuation.  As opposed to puffs_cc_continue() this
	   call returns immediately.  pcc will be scheduled sometime in the
	   future.

     puffs_cc_getcc(pu)
	   Returns the current pcc or NULL if this is the main thread.	NOTE:
	   The argument pu will most likely disappear at some point.

     Before calling puffs_cc_yield() a file system will typically want to
     record some cookie value into its own internal bookkeeping.  This cookie
     should be hooked to the pcc so that the correct continuation can be con‐
     tinued when the event it was waiting for triggers.	 Alternatively, the
     puffs_framebuf(3) framework and puffs_mainloop() can be used for handling
     this automatically.

SEE ALSO
     puffs(3), puffs_framebuf(3)

BSD			       January 28, 2008				   BSD

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome