… | |
… | |
20 | |
20 | |
21 | =head1 DESCRIPTION |
21 | =head1 DESCRIPTION |
22 | |
22 | |
23 | This module collection manages coroutines. Coroutines are similar |
23 | This module collection manages coroutines. Coroutines are similar |
24 | to threads but don't run in parallel at the same time even on SMP |
24 | to threads but don't run in parallel at the same time even on SMP |
25 | machines. The specific flavor of coroutine use din this module also |
25 | machines. The specific flavor of coroutine used in this module also |
26 | guarentees you that it will not switch between coroutines unless |
26 | guarantees you that it will not switch between coroutines unless |
27 | necessary, at easily-identified points in your program, so locking and |
27 | necessary, at easily-identified points in your program, so locking and |
28 | parallel access are rarely an issue, making coroutine programming much |
28 | parallel access are rarely an issue, making coroutine programming much |
29 | safer than threads programming. |
29 | safer than threads programming. |
30 | |
30 | |
31 | (Perl, however, does not natively support real threads but instead does a |
31 | (Perl, however, does not natively support real threads but instead does a |
… | |
… | |
50 | |
50 | |
51 | our $idle; # idle handler |
51 | our $idle; # idle handler |
52 | our $main; # main coroutine |
52 | our $main; # main coroutine |
53 | our $current; # current coroutine |
53 | our $current; # current coroutine |
54 | |
54 | |
55 | our $VERSION = '3.3'; |
55 | our $VERSION = '4.0'; |
56 | |
56 | |
57 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
57 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
58 | our %EXPORT_TAGS = ( |
58 | our %EXPORT_TAGS = ( |
59 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
59 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
60 | ); |
60 | ); |
… | |
… | |
108 | |
108 | |
109 | The current coroutine (the last coroutine switched to). The initial value |
109 | The current coroutine (the last coroutine switched to). The initial value |
110 | is C<$main> (of course). |
110 | is C<$main> (of course). |
111 | |
111 | |
112 | This variable is B<strictly> I<read-only>. It is provided for performance |
112 | This variable is B<strictly> I<read-only>. It is provided for performance |
113 | reasons. If performance is not essentiel you are encouraged to use the |
113 | reasons. If performance is not essential you are encouraged to use the |
114 | C<Coro::current> function instead. |
114 | C<Coro::current> function instead. |
115 | |
115 | |
116 | =cut |
116 | =cut |
117 | |
117 | |
|
|
118 | $main->{desc} = "[main::]"; |
|
|
119 | |
118 | # maybe some other module used Coro::Specific before... |
120 | # maybe some other module used Coro::Specific before... |
119 | $main->{specific} = $current->{specific} |
121 | $main->{_specific} = $current->{_specific} |
120 | if $current; |
122 | if $current; |
121 | |
123 | |
122 | _set_current $main; |
124 | _set_current $main; |
123 | |
125 | |
124 | sub current() { $current } |
126 | sub current() { $current } |
… | |
… | |
149 | # free coroutine data and mark as destructed |
151 | # free coroutine data and mark as destructed |
150 | $self->_destroy |
152 | $self->_destroy |
151 | or return; |
153 | or return; |
152 | |
154 | |
153 | # call all destruction callbacks |
155 | # call all destruction callbacks |
154 | $_->(@{$self->{status}}) |
156 | $_->(@{$self->{_status}}) |
155 | for @{(delete $self->{destroy_cb}) || []}; |
157 | for @{(delete $self->{_on_destroy}) || []}; |
156 | } |
158 | } |
157 | |
159 | |
158 | # this coroutine is necessary because a coroutine |
160 | # this coroutine is necessary because a coroutine |
159 | # cannot destroy itself. |
161 | # cannot destroy itself. |
160 | my @destroy; |
162 | my @destroy; |
… | |
… | |
166 | while @destroy; |
168 | while @destroy; |
167 | |
169 | |
168 | &schedule; |
170 | &schedule; |
169 | } |
171 | } |
170 | }; |
172 | }; |
171 | |
173 | $manager->desc ("[coro manager]"); |
172 | $manager->prio (PRIO_MAX); |
174 | $manager->prio (PRIO_MAX); |
173 | |
175 | |
174 | # static methods. not really. |
176 | # static methods. not really. |
175 | |
177 | |
176 | =back |
178 | =back |
… | |
… | |
185 | |
187 | |
186 | Create a new asynchronous coroutine and return it's coroutine object |
188 | Create a new asynchronous coroutine and return it's coroutine object |
187 | (usually unused). When the sub returns the new coroutine is automatically |
189 | (usually unused). When the sub returns the new coroutine is automatically |
188 | terminated. |
190 | terminated. |
189 | |
191 | |
190 | Calling C<exit> in a coroutine will not work correctly, so do not do that. |
192 | See the C<Coro::State::new> constructor for info about the coroutine |
|
|
193 | environment. |
191 | |
194 | |
192 | When the coroutine dies, the program will exit, just as in the main |
195 | Calling C<exit> in a coroutine will do the same as calling exit outside |
193 | program. |
196 | the coroutine. Likewise, when the coroutine dies, the program will exit, |
|
|
197 | just as it would in the main program. |
194 | |
198 | |
195 | # create a new coroutine that just prints its arguments |
199 | # create a new coroutine that just prints its arguments |
196 | async { |
200 | async { |
197 | print "@_\n"; |
201 | print "@_\n"; |
198 | } 1,2,3,4; |
202 | } 1,2,3,4; |
… | |
… | |
210 | Similar to C<async>, but uses a coroutine pool, so you should not call |
214 | Similar to C<async>, but uses a coroutine pool, so you should not call |
211 | terminate or join (although you are allowed to), and you get a coroutine |
215 | terminate or join (although you are allowed to), and you get a coroutine |
212 | that might have executed other code already (which can be good or bad :). |
216 | that might have executed other code already (which can be good or bad :). |
213 | |
217 | |
214 | Also, the block is executed in an C<eval> context and a warning will be |
218 | Also, the block is executed in an C<eval> context and a warning will be |
215 | issued in case of an exception instead of terminating the program, as C<async> does. |
219 | issued in case of an exception instead of terminating the program, as |
|
|
220 | C<async> does. As the coroutine is being reused, stuff like C<on_destroy> |
|
|
221 | will not work in the expected way, unless you call terminate or cancel, |
|
|
222 | which somehow defeats the purpose of pooling. |
216 | |
223 | |
217 | The priority will be reset to C<0> after each job, otherwise the coroutine |
224 | The priority will be reset to C<0> after each job, tracing will be |
218 | will be re-used "as-is". |
225 | disabled, the description will be reset and the default output filehandle |
|
|
226 | gets restored, so you can change alkl these. Otherwise the coroutine will |
|
|
227 | be re-used "as-is": most notably if you change other per-coroutine global |
|
|
228 | stuff such as C<$/> you need to revert that change, which is most simply |
|
|
229 | done by using local as in C< local $/ >. |
219 | |
230 | |
220 | The pool size is limited to 8 idle coroutines (this can be adjusted by |
231 | The pool size is limited to 8 idle coroutines (this can be adjusted by |
221 | changing $Coro::POOL_SIZE), and there can be as many non-idle coros as |
232 | changing $Coro::POOL_SIZE), and there can be as many non-idle coros as |
222 | required. |
233 | required. |
223 | |
234 | |
224 | If you are concerned about pooled coroutines growing a lot because a |
235 | If you are concerned about pooled coroutines growing a lot because a |
225 | single C<async_pool> used a lot of stackspace you can e.g. C<async_pool { |
236 | single C<async_pool> used a lot of stackspace you can e.g. C<async_pool |
226 | terminate }> once per second or so to slowly replenish the pool. |
237 | { terminate }> once per second or so to slowly replenish the pool. In |
|
|
238 | addition to that, when the stacks used by a handler grows larger than 16kb |
|
|
239 | (adjustable with $Coro::POOL_RSS) it will also exit. |
227 | |
240 | |
228 | =cut |
241 | =cut |
229 | |
242 | |
230 | our $POOL_SIZE = 8; |
243 | our $POOL_SIZE = 8; |
|
|
244 | our $POOL_RSS = 16 * 1024; |
231 | our @pool; |
245 | our @async_pool; |
232 | |
246 | |
233 | sub pool_handler { |
247 | sub pool_handler { |
|
|
248 | my $cb; |
|
|
249 | |
234 | while () { |
250 | while () { |
235 | my ($cb, @arg) = @{ delete $current->{_invoke} }; |
|
|
236 | |
|
|
237 | eval { |
251 | eval { |
238 | $cb->(@arg); |
252 | while () { |
|
|
253 | _pool_1 $cb; |
|
|
254 | &$cb; |
|
|
255 | _pool_2 $cb; |
|
|
256 | &schedule; |
|
|
257 | } |
239 | }; |
258 | }; |
|
|
259 | |
|
|
260 | last if $@ eq "\3terminate\2\n"; |
240 | warn $@ if $@; |
261 | warn $@ if $@; |
241 | |
|
|
242 | last if @pool >= $POOL_SIZE; |
|
|
243 | push @pool, $current; |
|
|
244 | |
|
|
245 | $current->prio (0); |
|
|
246 | schedule; |
|
|
247 | } |
262 | } |
248 | } |
263 | } |
249 | |
264 | |
250 | sub async_pool(&@) { |
265 | sub async_pool(&@) { |
251 | # this is also inlined into the unlock_scheduler |
266 | # this is also inlined into the unlock_scheduler |
252 | my $coro = (pop @pool or new Coro \&pool_handler); |
267 | my $coro = (pop @async_pool) || new Coro \&pool_handler; |
253 | |
268 | |
254 | $coro->{_invoke} = [@_]; |
269 | $coro->{_invoke} = [@_]; |
255 | $coro->ready; |
270 | $coro->ready; |
256 | |
271 | |
257 | $coro |
272 | $coro |
… | |
… | |
275 | # wake up sleeping coroutine |
290 | # wake up sleeping coroutine |
276 | $current->ready; |
291 | $current->ready; |
277 | undef $current; |
292 | undef $current; |
278 | }; |
293 | }; |
279 | |
294 | |
280 | # call schedule until event occured. |
295 | # call schedule until event occurred. |
281 | # in case we are woken up for other reasons |
296 | # in case we are woken up for other reasons |
282 | # (current still defined), loop. |
297 | # (current still defined), loop. |
283 | Coro::schedule while $current; |
298 | Coro::schedule while $current; |
284 | } |
299 | } |
285 | |
300 | |
… | |
… | |
300 | |
315 | |
301 | =item terminate [arg...] |
316 | =item terminate [arg...] |
302 | |
317 | |
303 | Terminates the current coroutine with the given status values (see L<cancel>). |
318 | Terminates the current coroutine with the given status values (see L<cancel>). |
304 | |
319 | |
|
|
320 | =item killall |
|
|
321 | |
|
|
322 | Kills/terminates/cancels all coroutines except the currently running |
|
|
323 | one. This is useful after a fork, either in the child or the parent, as |
|
|
324 | usually only one of them should inherit the running coroutines. |
|
|
325 | |
305 | =cut |
326 | =cut |
306 | |
327 | |
307 | sub terminate { |
328 | sub terminate { |
308 | $current->cancel (@_); |
329 | $current->cancel (@_); |
|
|
330 | } |
|
|
331 | |
|
|
332 | sub killall { |
|
|
333 | for (Coro::State::list) { |
|
|
334 | $_->cancel |
|
|
335 | if $_ != $current && UNIVERSAL::isa $_, "Coro"; |
|
|
336 | } |
309 | } |
337 | } |
310 | |
338 | |
311 | =back |
339 | =back |
312 | |
340 | |
313 | # dynamic methods |
341 | # dynamic methods |
… | |
… | |
323 | Create a new coroutine and return it. When the sub returns the coroutine |
351 | Create a new coroutine and return it. When the sub returns the coroutine |
324 | automatically terminates as if C<terminate> with the returned values were |
352 | automatically terminates as if C<terminate> with the returned values were |
325 | called. To make the coroutine run you must first put it into the ready queue |
353 | called. To make the coroutine run you must first put it into the ready queue |
326 | by calling the ready method. |
354 | by calling the ready method. |
327 | |
355 | |
328 | Calling C<exit> in a coroutine will not work correctly, so do not do that. |
356 | See C<async> and C<Coro::State::new> for additional info about the |
|
|
357 | coroutine environment. |
329 | |
358 | |
330 | =cut |
359 | =cut |
331 | |
360 | |
332 | sub _run_coro { |
361 | sub _run_coro { |
333 | terminate &{+shift}; |
362 | terminate &{+shift}; |
… | |
… | |
357 | |
386 | |
358 | =cut |
387 | =cut |
359 | |
388 | |
360 | sub cancel { |
389 | sub cancel { |
361 | my $self = shift; |
390 | my $self = shift; |
362 | $self->{status} = [@_]; |
391 | $self->{_status} = [@_]; |
363 | |
392 | |
364 | if ($current == $self) { |
393 | if ($current == $self) { |
365 | push @destroy, $self; |
394 | push @destroy, $self; |
366 | $manager->ready; |
395 | $manager->ready; |
367 | &schedule while 1; |
396 | &schedule while 1; |
… | |
… | |
371 | } |
400 | } |
372 | |
401 | |
373 | =item $coroutine->join |
402 | =item $coroutine->join |
374 | |
403 | |
375 | Wait until the coroutine terminates and return any values given to the |
404 | Wait until the coroutine terminates and return any values given to the |
376 | C<terminate> or C<cancel> functions. C<join> can be called multiple times |
405 | C<terminate> or C<cancel> functions. C<join> can be called concurrently |
377 | from multiple coroutine. |
406 | from multiple coroutines. |
378 | |
407 | |
379 | =cut |
408 | =cut |
380 | |
409 | |
381 | sub join { |
410 | sub join { |
382 | my $self = shift; |
411 | my $self = shift; |
383 | |
412 | |
384 | unless ($self->{status}) { |
413 | unless ($self->{_status}) { |
385 | my $current = $current; |
414 | my $current = $current; |
386 | |
415 | |
387 | push @{$self->{destroy_cb}}, sub { |
416 | push @{$self->{_on_destroy}}, sub { |
388 | $current->ready; |
417 | $current->ready; |
389 | undef $current; |
418 | undef $current; |
390 | }; |
419 | }; |
391 | |
420 | |
392 | &schedule while $current; |
421 | &schedule while $current; |
393 | } |
422 | } |
394 | |
423 | |
395 | wantarray ? @{$self->{status}} : $self->{status}[0]; |
424 | wantarray ? @{$self->{_status}} : $self->{_status}[0]; |
396 | } |
425 | } |
397 | |
426 | |
398 | =item $coroutine->on_destroy (\&cb) |
427 | =item $coroutine->on_destroy (\&cb) |
399 | |
428 | |
400 | Registers a callback that is called when this coroutine gets destroyed, |
429 | Registers a callback that is called when this coroutine gets destroyed, |
… | |
… | |
404 | =cut |
433 | =cut |
405 | |
434 | |
406 | sub on_destroy { |
435 | sub on_destroy { |
407 | my ($self, $cb) = @_; |
436 | my ($self, $cb) = @_; |
408 | |
437 | |
409 | push @{ $self->{destroy_cb} }, $cb; |
438 | push @{ $self->{_on_destroy} }, $cb; |
410 | } |
439 | } |
411 | |
440 | |
412 | =item $oldprio = $coroutine->prio ($newprio) |
441 | =item $oldprio = $coroutine->prio ($newprio) |
413 | |
442 | |
414 | Sets (or gets, if the argument is missing) the priority of the |
443 | Sets (or gets, if the argument is missing) the priority of the |
… | |
… | |
439 | =item $olddesc = $coroutine->desc ($newdesc) |
468 | =item $olddesc = $coroutine->desc ($newdesc) |
440 | |
469 | |
441 | Sets (or gets in case the argument is missing) the description for this |
470 | Sets (or gets in case the argument is missing) the description for this |
442 | coroutine. This is just a free-form string you can associate with a coroutine. |
471 | coroutine. This is just a free-form string you can associate with a coroutine. |
443 | |
472 | |
|
|
473 | This method simply sets the C<< $coroutine->{desc} >> member to the given string. You |
|
|
474 | can modify this member directly if you wish. |
|
|
475 | |
444 | =cut |
476 | =cut |
445 | |
477 | |
446 | sub desc { |
478 | sub desc { |
447 | my $old = $_[0]{desc}; |
479 | my $old = $_[0]{desc}; |
448 | $_[0]{desc} = $_[1] if @_ > 1; |
480 | $_[0]{desc} = $_[1] if @_ > 1; |
… | |
… | |
456 | =over 4 |
488 | =over 4 |
457 | |
489 | |
458 | =item Coro::nready |
490 | =item Coro::nready |
459 | |
491 | |
460 | Returns the number of coroutines that are currently in the ready state, |
492 | Returns the number of coroutines that are currently in the ready state, |
461 | i.e. that can be swicthed to. The value C<0> means that the only runnable |
493 | i.e. that can be switched to. The value C<0> means that the only runnable |
462 | coroutine is the currently running one, so C<cede> would have no effect, |
494 | coroutine is the currently running one, so C<cede> would have no effect, |
463 | and C<schedule> would cause a deadlock unless there is an idle handler |
495 | and C<schedule> would cause a deadlock unless there is an idle handler |
464 | that wakes up some coroutines. |
496 | that wakes up some coroutines. |
465 | |
497 | |
466 | =item my $guard = Coro::guard { ... } |
498 | =item my $guard = Coro::guard { ... } |
467 | |
499 | |
468 | This creates and returns a guard object. Nothing happens until the objetc |
500 | This creates and returns a guard object. Nothing happens until the object |
469 | gets destroyed, in which case the codeblock given as argument will be |
501 | gets destroyed, in which case the codeblock given as argument will be |
470 | executed. This is useful to free locks or other resources in case of a |
502 | executed. This is useful to free locks or other resources in case of a |
471 | runtime error or when the coroutine gets canceled, as in both cases the |
503 | runtime error or when the coroutine gets canceled, as in both cases the |
472 | guard block will be executed. The guard object supports only one method, |
504 | guard block will be executed. The guard object supports only one method, |
473 | C<< ->cancel >>, which will keep the codeblock from being executed. |
505 | C<< ->cancel >>, which will keep the codeblock from being executed. |
… | |
… | |
502 | This utility function takes a BLOCK or code reference and "unblocks" it, |
534 | This utility function takes a BLOCK or code reference and "unblocks" it, |
503 | returning the new coderef. This means that the new coderef will return |
535 | returning the new coderef. This means that the new coderef will return |
504 | immediately without blocking, returning nothing, while the original code |
536 | immediately without blocking, returning nothing, while the original code |
505 | ref will be called (with parameters) from within its own coroutine. |
537 | ref will be called (with parameters) from within its own coroutine. |
506 | |
538 | |
507 | The reason this fucntion exists is that many event libraries (such as the |
539 | The reason this function exists is that many event libraries (such as the |
508 | venerable L<Event|Event> module) are not coroutine-safe (a weaker form |
540 | venerable L<Event|Event> module) are not coroutine-safe (a weaker form |
509 | of thread-safety). This means you must not block within event callbacks, |
541 | of thread-safety). This means you must not block within event callbacks, |
510 | otherwise you might suffer from crashes or worse. |
542 | otherwise you might suffer from crashes or worse. |
511 | |
543 | |
512 | This function allows your callbacks to block by executing them in another |
544 | This function allows your callbacks to block by executing them in another |
… | |
… | |
523 | |
555 | |
524 | # we create a special coro because we want to cede, |
556 | # we create a special coro because we want to cede, |
525 | # to reduce pressure on the coro pool (because most callbacks |
557 | # to reduce pressure on the coro pool (because most callbacks |
526 | # return immediately and can be reused) and because we cannot cede |
558 | # return immediately and can be reused) and because we cannot cede |
527 | # inside an event callback. |
559 | # inside an event callback. |
528 | our $unblock_scheduler = async { |
560 | our $unblock_scheduler = new Coro sub { |
529 | while () { |
561 | while () { |
530 | while (my $cb = pop @unblock_queue) { |
562 | while (my $cb = pop @unblock_queue) { |
531 | # this is an inlined copy of async_pool |
563 | # this is an inlined copy of async_pool |
532 | my $coro = (pop @pool or new Coro \&pool_handler); |
564 | my $coro = (pop @async_pool) || new Coro \&pool_handler; |
533 | |
565 | |
534 | $coro->{_invoke} = $cb; |
566 | $coro->{_invoke} = $cb; |
535 | $coro->ready; |
567 | $coro->ready; |
536 | cede; # for short-lived callbacks, this reduces pressure on the coro pool |
568 | cede; # for short-lived callbacks, this reduces pressure on the coro pool |
537 | } |
569 | } |
538 | schedule; # sleep well |
570 | schedule; # sleep well |
539 | } |
571 | } |
540 | }; |
572 | }; |
|
|
573 | $unblock_scheduler->desc ("[unblock_sub scheduler]"); |
541 | |
574 | |
542 | sub unblock_sub(&) { |
575 | sub unblock_sub(&) { |
543 | my $cb = shift; |
576 | my $cb = shift; |
544 | |
577 | |
545 | sub { |
578 | sub { |
… | |
… | |
558 | |
591 | |
559 | - you must make very sure that no coro is still active on global |
592 | - you must make very sure that no coro is still active on global |
560 | destruction. very bad things might happen otherwise (usually segfaults). |
593 | destruction. very bad things might happen otherwise (usually segfaults). |
561 | |
594 | |
562 | - this module is not thread-safe. You should only ever use this module |
595 | - this module is not thread-safe. You should only ever use this module |
563 | from the same thread (this requirement might be losened in the future |
596 | from the same thread (this requirement might be loosened in the future |
564 | to allow per-thread schedulers, but Coro::State does not yet allow |
597 | to allow per-thread schedulers, but Coro::State does not yet allow |
565 | this). |
598 | this). |
566 | |
599 | |
567 | =head1 SEE ALSO |
600 | =head1 SEE ALSO |
568 | |
601 | |
569 | Support/Utility: L<Coro::Cont>, L<Coro::Specific>, L<Coro::State>, L<Coro::Util>. |
602 | Support/Utility: L<Coro::Specific>, L<Coro::State>, L<Coro::Util>. |
570 | |
603 | |
571 | Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>. |
604 | Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>. |
572 | |
605 | |
573 | Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::Select>. |
606 | Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::Select>. |
574 | |
607 | |