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

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines