Searched refs:reap (Results 1 – 17 of 17) sorted by relevance
120 link->next=vb->reap; in _vorbis_block_alloc()122 vb->reap=link; in _vorbis_block_alloc()139 struct alloc_chain *reap=vb->reap; in _vorbis_block_ripcord() local140 while(reap){ in _vorbis_block_ripcord()141 struct alloc_chain *next=reap->next; in _vorbis_block_ripcord()142 _ogg_free(reap->ptr); in _vorbis_block_ripcord()143 memset(reap,0,sizeof(*reap)); in _vorbis_block_ripcord()144 _ogg_free(reap); in _vorbis_block_ripcord()145 reap=next; in _vorbis_block_ripcord()156 vb->reap=NULL; in _vorbis_block_ripcord()
17 - Process creation - number of times a process can fork and reap18 - Shell Scripts - number of times a process can start and reap a script
19 - Process creation - number of times a process can fork and reap20 - Shell Scripts - number of times a process can start and reap a script
20 Your backend must also provide an event handling function to "reap" ongoing37 platform, you can emulate this using an internal library thread to reap I/O as
524 goto reap; in do_verify()630 reap: in do_verify()783 goto reap; in do_io()786 goto reap; in do_io()912 reap: in do_io()1916 goto reap; in run_threads()1924 reap: in run_threads()
1638 the io_getevents system call to reap newly returned events.1640 from user-space to reap events. The reaping mode is only
110 struct alloc_chain *reap; member
393 if args.reap:
47 \fB\-\-reap\fP
938 …A9QrealA realisation )J!AD'Q=0'F realization )J!AD'Q=0'Freally#J!AD+reap0rearAreasone…
2095 * run-native-test.sh: Do kill -9 and reap explicitly at end, since
2313 Handle EINTR returns from wait() correctly and reap
3925 自食其果 < reap\-what\-one\-has\-sown;5100 不勞而獲 < reap\-without\-sowing;20784 收割 < reap;22315 自食其果 > reap\-what\-one\-has\-sown;22464 不勞而獲 > reap\-without\-sowing;35252 收割 > reap;
4706 V "reap" :G2P
5221 V "reap" :G2P
3347 process has zombies it can reap. On the way out, if we reaped
11608 the spawned process and reap it when required.