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

Comparing Coro/Coro.pm (file contents):
Revision 1.115 by root, Wed Feb 28 11:43:03 2007 UTC vs.
Revision 1.145 by root, Wed Oct 3 16:03:17 2007 UTC

20 20
21=head1 DESCRIPTION 21=head1 DESCRIPTION
22 22
23This module collection manages coroutines. Coroutines are similar 23This module collection manages coroutines. Coroutines are similar
24to threads but don't run in parallel at the same time even on SMP 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 25machines. The specific flavor of coroutine used in this module also
26guarentees you that it will not switch between coroutines unless 26guarantees you that it will not switch between coroutines unless
27necessary, at easily-identified points in your program, so locking and 27necessary, at easily-identified points in your program, so locking and
28parallel access are rarely an issue, making coroutine programming much 28parallel access are rarely an issue, making coroutine programming much
29safer than threads programming. 29safer 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
51our $idle; # idle handler 51our $idle; # idle handler
52our $main; # main coroutine 52our $main; # main coroutine
53our $current; # current coroutine 53our $current; # current coroutine
54 54
55our $VERSION = '3.501'; 55our $VERSION = '4.0';
56 56
57our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); 57our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);
58our %EXPORT_TAGS = ( 58our %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
109The current coroutine (the last coroutine switched to). The initial value 109The current coroutine (the last coroutine switched to). The initial value
110is C<$main> (of course). 110is C<$main> (of course).
111 111
112This variable is B<strictly> I<read-only>. It is provided for performance 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 113reasons. If performance is not essential you are encouraged to use the
114C<Coro::current> function instead. 114C<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
124sub current() { $current } 126sub 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.
160my @destroy; 162my @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
186Create a new asynchronous coroutine and return it's coroutine object 188Create 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
188terminated. 190terminated.
189 191
190Calling C<exit> in a coroutine will not work correctly, so do not do that. 192See the C<Coro::State::new> constructor for info about the coroutine
193environment.
191 194
192When the coroutine dies, the program will exit, just as in the main 195Calling C<exit> in a coroutine will do the same as calling exit outside
193program. 196the coroutine. Likewise, when the coroutine dies, the program will exit,
197just 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;
223The pool size is limited to 8 idle coroutines (this can be adjusted by 227The pool size is limited to 8 idle coroutines (this can be adjusted by
224changing $Coro::POOL_SIZE), and there can be as many non-idle coros as 228changing $Coro::POOL_SIZE), and there can be as many non-idle coros as
225required. 229required.
226 230
227If you are concerned about pooled coroutines growing a lot because a 231If you are concerned about pooled coroutines growing a lot because a
228single C<async_pool> used a lot of stackspace you can e.g. C<async_pool { 232single C<async_pool> used a lot of stackspace you can e.g. C<async_pool
229terminate }> once per second or so to slowly replenish the pool. 233{ terminate }> once per second or so to slowly replenish the pool. In
234addition to that, when the stacks used by a handler grows larger than 16kb
235(adjustable with $Coro::POOL_RSS) it will also exit.
230 236
231=cut 237=cut
232 238
233our $POOL_SIZE = 8; 239our $POOL_SIZE = 8;
240our $POOL_RSS = 16 * 1024;
234our @pool; 241our @async_pool;
235 242
236sub pool_handler { 243sub pool_handler {
244 my $cb;
245
237 while () { 246 while () {
238 eval { 247 eval {
239 my ($cb, @arg) = @{ delete $current->{_invoke} or return }; 248 while () {
240 $cb->(@arg); 249 _pool_1 $cb;
250 &$cb;
251 _pool_2 $cb;
252 &schedule;
253 }
241 }; 254 };
255
256 last if $@ eq "\3terminate\2\n";
242 warn $@ if $@; 257 warn $@ if $@;
243
244 last if @pool >= $POOL_SIZE;
245 push @pool, $current;
246
247 $current->prio (0);
248 schedule;
249 } 258 }
250} 259}
251 260
252sub async_pool(&@) { 261sub async_pool(&@) {
253 # this is also inlined into the unlock_scheduler 262 # this is also inlined into the unlock_scheduler
254 my $coro = (pop @pool or new Coro \&pool_handler); 263 my $coro = (pop @async_pool) || new Coro \&pool_handler;
255 264
256 $coro->{_invoke} = [@_]; 265 $coro->{_invoke} = [@_];
257 $coro->ready; 266 $coro->ready;
258 267
259 $coro 268 $coro
277 # wake up sleeping coroutine 286 # wake up sleeping coroutine
278 $current->ready; 287 $current->ready;
279 undef $current; 288 undef $current;
280 }; 289 };
281 290
282 # call schedule until event occured. 291 # call schedule until event occurred.
283 # in case we are woken up for other reasons 292 # in case we are woken up for other reasons
284 # (current still defined), loop. 293 # (current still defined), loop.
285 Coro::schedule while $current; 294 Coro::schedule while $current;
286 } 295 }
287 296
302 311
303=item terminate [arg...] 312=item terminate [arg...]
304 313
305Terminates the current coroutine with the given status values (see L<cancel>). 314Terminates the current coroutine with the given status values (see L<cancel>).
306 315
316=item killall
317
318Kills/terminates/cancels all coroutines except the currently running
319one. This is useful after a fork, either in the child or the parent, as
320usually only one of them should inherit the running coroutines.
321
307=cut 322=cut
308 323
309sub terminate { 324sub terminate {
310 $current->cancel (@_); 325 $current->cancel (@_);
326}
327
328sub killall {
329 for (Coro::State::list) {
330 $_->cancel
331 if $_ != $current && UNIVERSAL::isa $_, "Coro";
332 }
311} 333}
312 334
313=back 335=back
314 336
315# dynamic methods 337# dynamic methods
325Create a new coroutine and return it. When the sub returns the coroutine 347Create a new coroutine and return it. When the sub returns the coroutine
326automatically terminates as if C<terminate> with the returned values were 348automatically terminates as if C<terminate> with the returned values were
327called. To make the coroutine run you must first put it into the ready queue 349called. To make the coroutine run you must first put it into the ready queue
328by calling the ready method. 350by calling the ready method.
329 351
330Calling C<exit> in a coroutine will not work correctly, so do not do that. 352See C<async> and C<Coro::State::new> for additional info about the
353coroutine environment.
331 354
332=cut 355=cut
333 356
334sub _run_coro { 357sub _run_coro {
335 terminate &{+shift}; 358 terminate &{+shift};
359 382
360=cut 383=cut
361 384
362sub cancel { 385sub cancel {
363 my $self = shift; 386 my $self = shift;
364 $self->{status} = [@_]; 387 $self->{_status} = [@_];
365 388
366 if ($current == $self) { 389 if ($current == $self) {
367 push @destroy, $self; 390 push @destroy, $self;
368 $manager->ready; 391 $manager->ready;
369 &schedule while 1; 392 &schedule while 1;
373} 396}
374 397
375=item $coroutine->join 398=item $coroutine->join
376 399
377Wait until the coroutine terminates and return any values given to the 400Wait until the coroutine terminates and return any values given to the
378C<terminate> or C<cancel> functions. C<join> can be called multiple times 401C<terminate> or C<cancel> functions. C<join> can be called concurrently
379from multiple coroutine. 402from multiple coroutines.
380 403
381=cut 404=cut
382 405
383sub join { 406sub join {
384 my $self = shift; 407 my $self = shift;
385 408
386 unless ($self->{status}) { 409 unless ($self->{_status}) {
387 my $current = $current; 410 my $current = $current;
388 411
389 push @{$self->{destroy_cb}}, sub { 412 push @{$self->{_on_destroy}}, sub {
390 $current->ready; 413 $current->ready;
391 undef $current; 414 undef $current;
392 }; 415 };
393 416
394 &schedule while $current; 417 &schedule while $current;
395 } 418 }
396 419
397 wantarray ? @{$self->{status}} : $self->{status}[0]; 420 wantarray ? @{$self->{_status}} : $self->{_status}[0];
398} 421}
399 422
400=item $coroutine->on_destroy (\&cb) 423=item $coroutine->on_destroy (\&cb)
401 424
402Registers a callback that is called when this coroutine gets destroyed, 425Registers a callback that is called when this coroutine gets destroyed,
406=cut 429=cut
407 430
408sub on_destroy { 431sub on_destroy {
409 my ($self, $cb) = @_; 432 my ($self, $cb) = @_;
410 433
411 push @{ $self->{destroy_cb} }, $cb; 434 push @{ $self->{_on_destroy} }, $cb;
412} 435}
413 436
414=item $oldprio = $coroutine->prio ($newprio) 437=item $oldprio = $coroutine->prio ($newprio)
415 438
416Sets (or gets, if the argument is missing) the priority of the 439Sets (or gets, if the argument is missing) the priority of the
441=item $olddesc = $coroutine->desc ($newdesc) 464=item $olddesc = $coroutine->desc ($newdesc)
442 465
443Sets (or gets in case the argument is missing) the description for this 466Sets (or gets in case the argument is missing) the description for this
444coroutine. This is just a free-form string you can associate with a coroutine. 467coroutine. This is just a free-form string you can associate with a coroutine.
445 468
469This method simply sets the C<< $coroutine->{desc} >> member to the given string. You
470can modify this member directly if you wish.
471
446=cut 472=cut
447 473
448sub desc { 474sub desc {
449 my $old = $_[0]{desc}; 475 my $old = $_[0]{desc};
450 $_[0]{desc} = $_[1] if @_ > 1; 476 $_[0]{desc} = $_[1] if @_ > 1;
458=over 4 484=over 4
459 485
460=item Coro::nready 486=item Coro::nready
461 487
462Returns the number of coroutines that are currently in the ready state, 488Returns the number of coroutines that are currently in the ready state,
463i.e. that can be swicthed to. The value C<0> means that the only runnable 489i.e. that can be switched to. The value C<0> means that the only runnable
464coroutine is the currently running one, so C<cede> would have no effect, 490coroutine is the currently running one, so C<cede> would have no effect,
465and C<schedule> would cause a deadlock unless there is an idle handler 491and C<schedule> would cause a deadlock unless there is an idle handler
466that wakes up some coroutines. 492that wakes up some coroutines.
467 493
468=item my $guard = Coro::guard { ... } 494=item my $guard = Coro::guard { ... }
469 495
470This creates and returns a guard object. Nothing happens until the objetc 496This creates and returns a guard object. Nothing happens until the object
471gets destroyed, in which case the codeblock given as argument will be 497gets destroyed, in which case the codeblock given as argument will be
472executed. This is useful to free locks or other resources in case of a 498executed. This is useful to free locks or other resources in case of a
473runtime error or when the coroutine gets canceled, as in both cases the 499runtime error or when the coroutine gets canceled, as in both cases the
474guard block will be executed. The guard object supports only one method, 500guard block will be executed. The guard object supports only one method,
475C<< ->cancel >>, which will keep the codeblock from being executed. 501C<< ->cancel >>, which will keep the codeblock from being executed.
504This utility function takes a BLOCK or code reference and "unblocks" it, 530This utility function takes a BLOCK or code reference and "unblocks" it,
505returning the new coderef. This means that the new coderef will return 531returning the new coderef. This means that the new coderef will return
506immediately without blocking, returning nothing, while the original code 532immediately without blocking, returning nothing, while the original code
507ref will be called (with parameters) from within its own coroutine. 533ref will be called (with parameters) from within its own coroutine.
508 534
509The reason this fucntion exists is that many event libraries (such as the 535The reason this function exists is that many event libraries (such as the
510venerable L<Event|Event> module) are not coroutine-safe (a weaker form 536venerable L<Event|Event> module) are not coroutine-safe (a weaker form
511of thread-safety). This means you must not block within event callbacks, 537of thread-safety). This means you must not block within event callbacks,
512otherwise you might suffer from crashes or worse. 538otherwise you might suffer from crashes or worse.
513 539
514This function allows your callbacks to block by executing them in another 540This function allows your callbacks to block by executing them in another
525 551
526# we create a special coro because we want to cede, 552# we create a special coro because we want to cede,
527# to reduce pressure on the coro pool (because most callbacks 553# to reduce pressure on the coro pool (because most callbacks
528# return immediately and can be reused) and because we cannot cede 554# return immediately and can be reused) and because we cannot cede
529# inside an event callback. 555# inside an event callback.
530our $unblock_scheduler = async { 556our $unblock_scheduler = new Coro sub {
531 while () { 557 while () {
532 while (my $cb = pop @unblock_queue) { 558 while (my $cb = pop @unblock_queue) {
533 # this is an inlined copy of async_pool 559 # this is an inlined copy of async_pool
534 my $coro = (pop @pool or new Coro \&pool_handler); 560 my $coro = (pop @async_pool) || new Coro \&pool_handler;
535 561
536 $coro->{_invoke} = $cb; 562 $coro->{_invoke} = $cb;
537 $coro->ready; 563 $coro->ready;
538 cede; # for short-lived callbacks, this reduces pressure on the coro pool 564 cede; # for short-lived callbacks, this reduces pressure on the coro pool
539 } 565 }
540 schedule; # sleep well 566 schedule; # sleep well
541 } 567 }
542}; 568};
569$unblock_scheduler->desc ("[unblock_sub scheduler]");
543 570
544sub unblock_sub(&) { 571sub unblock_sub(&) {
545 my $cb = shift; 572 my $cb = shift;
546 573
547 sub { 574 sub {
560 587
561 - you must make very sure that no coro is still active on global 588 - you must make very sure that no coro is still active on global
562 destruction. very bad things might happen otherwise (usually segfaults). 589 destruction. very bad things might happen otherwise (usually segfaults).
563 590
564 - this module is not thread-safe. You should only ever use this module 591 - this module is not thread-safe. You should only ever use this module
565 from the same thread (this requirement might be losened in the future 592 from the same thread (this requirement might be loosened in the future
566 to allow per-thread schedulers, but Coro::State does not yet allow 593 to allow per-thread schedulers, but Coro::State does not yet allow
567 this). 594 this).
568 595
569=head1 SEE ALSO 596=head1 SEE ALSO
570 597

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines