ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/Coro/Coro.pm
(Generate patch)

Comparing Coro/Coro.pm (file contents):
Revision 1.13 by root, Tue Jul 17 00:24:14 2001 UTC vs.
Revision 1.102 by root, Fri Dec 29 11:37:49 2006 UTC

8 8
9 async { 9 async {
10 # some asynchronous thread of execution 10 # some asynchronous thread of execution
11 }; 11 };
12 12
13 # alternatively create an async process like this: 13 # alternatively create an async coroutine like this:
14 14
15 sub some_func : Coro { 15 sub some_func : Coro {
16 # some more async code 16 # some more async code
17 } 17 }
18 18
19 yield; 19 cede;
20 20
21=head1 DESCRIPTION 21=head1 DESCRIPTION
22 22
23This module collection manages coroutines. Coroutines are similar
24to threads but don't run in parallel at the same time even on SMP
25machines. The specific flavor of coroutine use din this module also
26guarentees you that it will not switch between coroutines unless
27necessary, at easily-identified points in your program, so locking and
28parallel access are rarely an issue, making coroutine programming much
29safer than threads programming.
30
31(Perl, however, does not natively support real threads but instead does a
32very slow and memory-intensive emulation of processes using threads. This
33is a performance win on Windows machines, and a loss everywhere else).
34
35In this module, coroutines are defined as "callchain + lexical variables +
36@_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own callchain,
37its own set of lexicals and its own set of perls most important global
38variables.
39
23=cut 40=cut
24 41
25package Coro; 42package Coro;
26 43
44use strict;
45no warnings "uninitialized";
46
27use Coro::State; 47use Coro::State;
28 48
29use base Exporter; 49use base qw(Coro::State Exporter);
30 50
31$VERSION = 0.05; 51our $idle; # idle handler
52our $main; # main coroutine
53our $current; # current coroutine
32 54
33@EXPORT = qw(async yield schedule terminate); 55our $VERSION = '3.3';
34@EXPORT_OK = qw($current); 56
57our @EXPORT = qw(async cede schedule terminate current unblock_sub);
58our %EXPORT_TAGS = (
59 prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
60);
61our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready));
35 62
36{ 63{
37 use subs 'async';
38
39 my @async; 64 my @async;
65 my $init;
40 66
41 # this way of handling attributes simply is NOT scalable ;() 67 # this way of handling attributes simply is NOT scalable ;()
42 sub import { 68 sub import {
69 no strict 'refs';
70
43 Coro->export_to_level(1, @_); 71 Coro->export_to_level (1, @_);
72
44 my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE}; 73 my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};
45 *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"} = sub { 74 *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"} = sub {
46 my ($package, $ref) = (shift, shift); 75 my ($package, $ref) = (shift, shift);
47 my @attrs; 76 my @attrs;
48 for (@_) { 77 for (@_) {
49 if ($_ eq "Coro") { 78 if ($_ eq "Coro") {
50 push @async, $ref; 79 push @async, $ref;
80 unless ($init++) {
81 eval q{
82 sub INIT {
83 &async(pop @async) while @async;
84 }
85 };
86 }
51 } else { 87 } else {
52 push @attrs, @_; 88 push @attrs, $_;
53 } 89 }
54 } 90 }
55 return $old ? $old->($package, $name, @attrs) : @attrs; 91 return $old ? $old->($package, $ref, @attrs) : @attrs;
56 }; 92 };
57 } 93 }
58 94
59 sub INIT {
60 async pop @async while @async;
61 }
62} 95}
96
97=over 4
63 98
64=item $main 99=item $main
65 100
66This coroutine represents the main program. 101This coroutine represents the main program.
67 102
68=cut 103=cut
69 104
70our $main = new Coro; 105$main = new Coro;
71 106
72=item $current 107=item $current (or as function: current)
73 108
74The current coroutine (the last coroutine switched to). The initial value is C<$main> (of course). 109The current coroutine (the last coroutine switched to). The initial value
110is C<$main> (of course).
111
112This variable is B<strictly> I<read-only>. It is provided for performance
113reasons. If performance is not essentiel you are encouraged to use the
114C<Coro::current> function instead.
75 115
76=cut 116=cut
77 117
78# maybe some other module used Coro::Specific before... 118# maybe some other module used Coro::Specific before...
79if ($current) {
80 $main->{specific} = $current->{specific}; 119$main->{specific} = $current->{specific}
81} 120 if $current;
82 121
83our $current = $main; 122_set_current $main;
123
124sub current() { $current }
84 125
85=item $idle 126=item $idle
86 127
87The coroutine to switch to when no other coroutine is running. The default 128A callback that is called whenever the scheduler finds no ready coroutines
88implementation prints "FATAL: deadlock detected" and exits. 129to run. The default implementation prints "FATAL: deadlock detected" and
130exits, because the program has no other way to continue.
89 131
90=cut 132This hook is overwritten by modules such as C<Coro::Timer> and
133C<Coro::Event> to wait on an external event that hopefully wake up a
134coroutine so the scheduler can run it.
91 135
92# should be done using priorities :( 136Please note that if your callback recursively invokes perl (e.g. for event
93our $idle = new Coro sub { 137handlers), then it must be prepared to be called recursively.
94 print STDERR "FATAL: deadlock detected\n"; 138
95 exit(51); 139=cut
140
141$idle = sub {
142 require Carp;
143 Carp::croak ("FATAL: deadlock detected");
96}; 144};
97 145
98# we really need priorities... 146# this coroutine is necessary because a coroutine
99## my @ready; #d# 147# cannot destroy itself.
100our @ready = (); # the ready queue. hehe, rather broken ;) 148my @destroy;
149my $manager; $manager = new Coro sub {
150 while () {
151 # by overwriting the state object with the manager we destroy it
152 # while still being able to schedule this coroutine (in case it has
153 # been readied multiple times. this is harmless since the manager
154 # can be called as many times as neccessary and will always
155 # remove itself from the runqueue
156 while (@destroy) {
157 my $coro = pop @destroy;
158
159 $coro->{status} ||= [];
160
161 $_->ready for @{(delete $coro->{join} ) || []};
162 $_->(@{$coro->{status}}) for @{(delete $coro->{destroy_cb}) || []};
163
164 # the next line destroys the coro state, but keeps the
165 # coroutine itself intact (we basically make it a zombie
166 # coroutine that always runs the manager thread, so it's possible
167 # to transfer() to this coroutine).
168 $coro->_clone_state_from ($manager);
169 }
170 &schedule;
171 }
172};
101 173
102# static methods. not really. 174# static methods. not really.
103 175
176=back
177
104=head2 STATIC METHODS 178=head2 STATIC METHODS
105 179
106Static methods are actually functions that operate on the current process only. 180Static methods are actually functions that operate on the current coroutine only.
107 181
108=over 4 182=over 4
109 183
110=item async { ... } [@args...] 184=item async { ... } [@args...]
111 185
112Create a new asynchronous process and return it's process object 186Create a new asynchronous coroutine and return it's coroutine object
113(usually unused). When the sub returns the new process is automatically 187(usually unused). When the sub returns the new coroutine is automatically
114terminated. 188terminated.
189
190Calling C<exit> in a coroutine will not work correctly, so do not do that.
191
192When the coroutine dies, the program will exit, just as in the main
193program.
115 194
116 # create a new coroutine that just prints its arguments 195 # create a new coroutine that just prints its arguments
117 async { 196 async {
118 print "@_\n"; 197 print "@_\n";
119 } 1,2,3,4; 198 } 1,2,3,4;
120 199
121The coderef you submit MUST NOT be a closure that refers to variables
122in an outer scope. This does NOT work. Pass arguments into it instead.
123
124=cut 200=cut
125 201
126sub async(&@) { 202sub async(&@) {
127 my $pid = new Coro @_; 203 my $pid = new Coro @_;
128 $pid->ready; 204 $pid->ready;
129 $pid; 205 $pid
130} 206}
131 207
132=item schedule 208=item schedule
133 209
134Calls the scheduler. Please note that the current process will not be put 210Calls the scheduler. Please note that the current coroutine will not be put
135into the ready queue, so calling this function usually means you will 211into the ready queue, so calling this function usually means you will
136never be called again. 212never be called again unless something else (e.g. an event handler) calls
213ready.
137 214
138=cut 215The canonical way to wait on external events is this:
139 216
140my $prev; 217 {
218 # remember current coroutine
219 my $current = $Coro::current;
141 220
142sub schedule { 221 # register a hypothetical event handler
143 # should be done using priorities :( 222 on_event_invoke sub {
144 ($prev, $current) = ($current, shift @ready || $idle); 223 # wake up sleeping coroutine
145 Coro::State::transfer($prev, $current);
146}
147
148=item yield
149
150Yield to other processes. This function puts the current process into the
151ready queue and calls C<schedule>.
152
153=cut
154
155sub yield {
156 $current->ready; 224 $current->ready;
157 &schedule; 225 undef $current;
158} 226 };
159 227
228 # call schedule until event occured.
229 # in case we are woken up for other reasons
230 # (current still defined), loop.
231 Coro::schedule while $current;
232 }
233
234=item cede
235
236"Cede" to other coroutines. This function puts the current coroutine into the
237ready queue and calls C<schedule>, which has the effect of giving up the
238current "timeslice" to other coroutines of the same or higher priority.
239
240=item Coro::cede_notself
241
242Works like cede, but is not exported by default and will cede to any
243coroutine, regardless of priority, once.
244
160=item terminate 245=item terminate [arg...]
161 246
162Terminates the current process. 247Terminates the current coroutine with the given status values (see L<cancel>).
163
164Future versions of this function will allow result arguments.
165 248
166=cut 249=cut
167 250
168sub terminate { 251sub terminate {
169 $current->{_results} = [@_]; 252 $current->cancel (@_);
170 &schedule;
171} 253}
172 254
173=back 255=back
174 256
175# dynamic methods 257# dynamic methods
176 258
177=head2 PROCESS METHODS 259=head2 COROUTINE METHODS
178 260
179These are the methods you can call on process objects. 261These are the methods you can call on coroutine objects.
180 262
181=over 4 263=over 4
182 264
183=item new Coro \&sub [, @args...] 265=item new Coro \&sub [, @args...]
184 266
185Create a new process and return it. When the sub returns the process 267Create a new coroutine and return it. When the sub returns the coroutine
186automatically terminates. To start the process you must first put it into 268automatically terminates as if C<terminate> with the returned values were
269called. To make the coroutine run you must first put it into the ready queue
187the ready queue by calling the ready method. 270by calling the ready method.
188 271
189The coderef you submit MUST NOT be a closure that refers to variables 272Calling C<exit> in a coroutine will not work correctly, so do not do that.
190in an outer scope. This does NOT work. Pass arguments into it instead.
191 273
192=cut 274=cut
193 275
194sub _newcoro { 276sub _run_coro {
195 terminate &{+shift}; 277 terminate &{+shift};
196} 278}
197 279
198sub new { 280sub new {
199 my $class = shift; 281 my $class = shift;
200 bless {
201 _coro_state => (new Coro::State $_[0] && \&_newcoro, @_),
202 }, $class;
203}
204 282
205=item $process->ready 283 $class->SUPER::new (\&_run_coro, @_)
284}
206 285
207Put the current process into the ready queue. 286=item $success = $coroutine->ready
208 287
209=cut 288Put the given coroutine into the ready queue (according to it's priority)
289and return true. If the coroutine is already in the ready queue, do nothing
290and return false.
210 291
211sub ready { 292=item $is_ready = $coroutine->is_ready
212 push @ready, $_[0]; 293
294Return wether the coroutine is currently the ready queue or not,
295
296=item $coroutine->cancel (arg...)
297
298Terminates the given coroutine and makes it return the given arguments as
299status (default: the empty list).
300
301=cut
302
303sub cancel {
304 my $self = shift;
305 $self->{status} = [@_];
306 push @destroy, $self;
307 $manager->ready;
308 &schedule if $current == $self;
309}
310
311=item $coroutine->join
312
313Wait until the coroutine terminates and return any values given to the
314C<terminate> or C<cancel> functions. C<join> can be called multiple times
315from multiple coroutine.
316
317=cut
318
319sub join {
320 my $self = shift;
321 unless ($self->{status}) {
322 push @{$self->{join}}, $current;
323 &schedule;
324 }
325 wantarray ? @{$self->{status}} : $self->{status}[0];
326}
327
328=item $coroutine->on_destroy (\&cb)
329
330Registers a callback that is called when this coroutine gets destroyed,
331but before it is joined. The callback gets passed the terminate arguments,
332if any.
333
334=cut
335
336sub on_destroy {
337 my ($self, $cb) = @_;
338
339 push @{ $self->{destroy_cb} }, $cb;
340}
341
342=item $oldprio = $coroutine->prio ($newprio)
343
344Sets (or gets, if the argument is missing) the priority of the
345coroutine. Higher priority coroutines get run before lower priority
346coroutines. Priorities are small signed integers (currently -4 .. +3),
347that you can refer to using PRIO_xxx constants (use the import tag :prio
348to get then):
349
350 PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN
351 3 > 1 > 0 > -1 > -3 > -4
352
353 # set priority to HIGH
354 current->prio(PRIO_HIGH);
355
356The idle coroutine ($Coro::idle) always has a lower priority than any
357existing coroutine.
358
359Changing the priority of the current coroutine will take effect immediately,
360but changing the priority of coroutines in the ready queue (but not
361running) will only take effect after the next schedule (of that
362coroutine). This is a bug that will be fixed in some future version.
363
364=item $newprio = $coroutine->nice ($change)
365
366Similar to C<prio>, but subtract the given value from the priority (i.e.
367higher values mean lower priority, just as in unix).
368
369=item $olddesc = $coroutine->desc ($newdesc)
370
371Sets (or gets in case the argument is missing) the description for this
372coroutine. This is just a free-form string you can associate with a coroutine.
373
374=cut
375
376sub desc {
377 my $old = $_[0]{desc};
378 $_[0]{desc} = $_[1] if @_ > 1;
379 $old;
213} 380}
214 381
215=back 382=back
216 383
384=head2 GLOBAL FUNCTIONS
385
386=over 4
387
388=item Coro::nready
389
390Returns the number of coroutines that are currently in the ready state,
391i.e. that can be swicthed to. The value C<0> means that the only runnable
392coroutine is the currently running one, so C<cede> would have no effect,
393and C<schedule> would cause a deadlock unless there is an idle handler
394that wakes up some coroutines.
395
396=item unblock_sub { ... }
397
398This utility function takes a BLOCK or code reference and "unblocks" it,
399returning the new coderef. This means that the new coderef will return
400immediately without blocking, returning nothing, while the original code
401ref will be called (with parameters) from within its own coroutine.
402
403The reason this fucntion exists is that many event libraries (such as the
404venerable L<Event|Event> module) are not coroutine-safe (a weaker form
405of thread-safety). This means you must not block within event callbacks,
406otherwise you might suffer from crashes or worse.
407
408This function allows your callbacks to block by executing them in another
409coroutine where it is safe to block. One example where blocking is handy
410is when you use the L<Coro::AIO|Coro::AIO> functions to save results to
411disk.
412
413In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when
414creating event callbacks that want to block.
415
416=cut
417
418our @unblock_pool;
419our @unblock_queue;
420our $UNBLOCK_POOL_SIZE = 2;
421
422sub unblock_handler_ {
423 while () {
424 my ($cb, @arg) = @{ delete $Coro::current->{arg} };
425 $cb->(@arg);
426
427 last if @unblock_pool >= $UNBLOCK_POOL_SIZE;
428 push @unblock_pool, $Coro::current;
429 schedule;
430 }
431}
432
433our $unblock_scheduler = async {
434 while () {
435 while (my $cb = pop @unblock_queue) {
436 my $handler = (pop @unblock_pool or new Coro \&unblock_handler_);
437 $handler->{arg} = $cb;
438 $handler->ready;
439 cede;
440 }
441
442 schedule;
443 }
444};
445
446sub unblock_sub(&) {
447 my $cb = shift;
448
449 sub {
450 push @unblock_queue, [$cb, @_];
451 $unblock_scheduler->ready;
452 }
453}
454
455=back
456
217=cut 457=cut
218 458
2191; 4591;
220 460
461=head1 BUGS/LIMITATIONS
462
463 - you must make very sure that no coro is still active on global
464 destruction. very bad things might happen otherwise (usually segfaults).
465
466 - this module is not thread-safe. You should only ever use this module
467 from the same thread (this requirement might be losened in the future
468 to allow per-thread schedulers, but Coro::State does not yet allow
469 this).
470
221=head1 SEE ALSO 471=head1 SEE ALSO
222 472
223L<Coro::Channel>, L<Coro::Cont>, L<Coro::Specific>, L<Coro::Semaphore>, 473Support/Utility: L<Coro::Cont>, L<Coro::Specific>, L<Coro::State>, L<Coro::Util>.
224L<Coro::Signal>, L<Coro::State>, L<Coro::Event>. 474
475Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>.
476
477Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::Select>.
478
479Embedding: L<Coro:MakeMaker>
225 480
226=head1 AUTHOR 481=head1 AUTHOR
227 482
228 Marc Lehmann <pcg@goof.com> 483 Marc Lehmann <schmorp@schmorp.de>
229 http://www.goof.com/pcg/marc/ 484 http://home.schmorp.de/
230 485
231=cut 486=cut
232 487

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines