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

Comparing Coro/Coro.pm (file contents):
Revision 1.119 by root, Wed Mar 28 14:24:17 2007 UTC vs.
Revision 1.162 by root, Wed Dec 12 19:09:33 2007 UTC

6 6
7 use Coro; 7 use Coro;
8 8
9 async { 9 async {
10 # some asynchronous thread of execution 10 # some asynchronous thread of execution
11 print "2\n";
12 cede; # yield back to main
13 print "4\n";
11 }; 14 };
15 print "1\n";
16 cede; # yield to coroutine
17 print "3\n";
18 cede; # and again
12 19
13 # alternatively create an async coroutine like this: 20 # use locking
21 my $lock = new Coro::Semaphore;
22 my $locked;
14 23
15 sub some_func : Coro { 24 $lock->down;
16 # some more async code 25 $locked = 1;
17 } 26 $lock->up;
18
19 cede;
20 27
21=head1 DESCRIPTION 28=head1 DESCRIPTION
22 29
23This module collection manages coroutines. Coroutines are similar 30This module collection manages coroutines. Coroutines are similar
24to threads but don't run in parallel at the same time even on SMP 31to 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 32machines. The specific flavor of coroutine used in this module also
26guarentees you that it will not switch between coroutines unless 33guarantees you that it will not switch between coroutines unless
27necessary, at easily-identified points in your program, so locking and 34necessary, at easily-identified points in your program, so locking and
28parallel access are rarely an issue, making coroutine programming much 35parallel access are rarely an issue, making coroutine programming much
29safer than threads programming. 36safer than threads programming.
30 37
31(Perl, however, does not natively support real threads but instead does a 38(Perl, however, does not natively support real threads but instead does a
33is a performance win on Windows machines, and a loss everywhere else). 40is a performance win on Windows machines, and a loss everywhere else).
34 41
35In this module, coroutines are defined as "callchain + lexical variables + 42In this module, coroutines are defined as "callchain + lexical variables +
36@_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own callchain, 43@_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own callchain,
37its own set of lexicals and its own set of perls most important global 44its own set of lexicals and its own set of perls most important global
38variables. 45variables (see L<Coro::State> for more configuration).
39 46
40=cut 47=cut
41 48
42package Coro; 49package Coro;
43 50
50 57
51our $idle; # idle handler 58our $idle; # idle handler
52our $main; # main coroutine 59our $main; # main coroutine
53our $current; # current coroutine 60our $current; # current coroutine
54 61
55our $VERSION = '3.55'; 62our $VERSION = '4.31';
56 63
57our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); 64our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);
58our %EXPORT_TAGS = ( 65our %EXPORT_TAGS = (
59 prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], 66 prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
60); 67);
108 115
109The current coroutine (the last coroutine switched to). The initial value 116The current coroutine (the last coroutine switched to). The initial value
110is C<$main> (of course). 117is C<$main> (of course).
111 118
112This variable is B<strictly> I<read-only>. It is provided for performance 119This variable is B<strictly> I<read-only>. It is provided for performance
113reasons. If performance is not essentiel you are encouraged to use the 120reasons. If performance is not essential you are encouraged to use the
114C<Coro::current> function instead. 121C<Coro::current> function instead.
115 122
116=cut 123=cut
117 124
125$main->{desc} = "[main::]";
126
118# maybe some other module used Coro::Specific before... 127# maybe some other module used Coro::Specific before...
119$main->{specific} = $current->{specific} 128$main->{_specific} = $current->{_specific}
120 if $current; 129 if $current;
121 130
122_set_current $main; 131_set_current $main;
123 132
124sub current() { $current } 133sub current() { $current }
132This hook is overwritten by modules such as C<Coro::Timer> and 141This 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 142C<Coro::Event> to wait on an external event that hopefully wake up a
134coroutine so the scheduler can run it. 143coroutine so the scheduler can run it.
135 144
136Please note that if your callback recursively invokes perl (e.g. for event 145Please note that if your callback recursively invokes perl (e.g. for event
137handlers), then it must be prepared to be called recursively. 146handlers), then it must be prepared to be called recursively itself.
138 147
139=cut 148=cut
140 149
141$idle = sub { 150$idle = sub {
142 require Carp; 151 require Carp;
149 # free coroutine data and mark as destructed 158 # free coroutine data and mark as destructed
150 $self->_destroy 159 $self->_destroy
151 or return; 160 or return;
152 161
153 # call all destruction callbacks 162 # call all destruction callbacks
154 $_->(@{$self->{status}}) 163 $_->(@{$self->{_status}})
155 for @{(delete $self->{destroy_cb}) || []}; 164 for @{(delete $self->{_on_destroy}) || []};
156} 165}
157 166
158# this coroutine is necessary because a coroutine 167# this coroutine is necessary because a coroutine
159# cannot destroy itself. 168# cannot destroy itself.
160my @destroy; 169my @destroy;
166 while @destroy; 175 while @destroy;
167 176
168 &schedule; 177 &schedule;
169 } 178 }
170}; 179};
171 180$manager->desc ("[coro manager]");
172$manager->prio (PRIO_MAX); 181$manager->prio (PRIO_MAX);
173 182
174# static methods. not really. 183# static methods. not really.
175 184
176=back 185=back
185 194
186Create a new asynchronous coroutine and return it's coroutine object 195Create a new asynchronous coroutine and return it's coroutine object
187(usually unused). When the sub returns the new coroutine is automatically 196(usually unused). When the sub returns the new coroutine is automatically
188terminated. 197terminated.
189 198
190Calling C<exit> in a coroutine will not work correctly, so do not do that. 199See the C<Coro::State::new> constructor for info about the coroutine
200environment in which coroutines run.
191 201
192When the coroutine dies, the program will exit, just as in the main 202Calling C<exit> in a coroutine will do the same as calling exit outside
193program. 203the coroutine. Likewise, when the coroutine dies, the program will exit,
204just as it would in the main program.
194 205
195 # create a new coroutine that just prints its arguments 206 # create a new coroutine that just prints its arguments
196 async { 207 async {
197 print "@_\n"; 208 print "@_\n";
198 } 1,2,3,4; 209 } 1,2,3,4;
215issued in case of an exception instead of terminating the program, as 226issued in case of an exception instead of terminating the program, as
216C<async> does. As the coroutine is being reused, stuff like C<on_destroy> 227C<async> does. As the coroutine is being reused, stuff like C<on_destroy>
217will not work in the expected way, unless you call terminate or cancel, 228will not work in the expected way, unless you call terminate or cancel,
218which somehow defeats the purpose of pooling. 229which somehow defeats the purpose of pooling.
219 230
220The priority will be reset to C<0> after each job, otherwise the coroutine 231The priority will be reset to C<0> after each job, tracing will be
221will be re-used "as-is". 232disabled, the description will be reset and the default output filehandle
233gets restored, so you can change alkl these. Otherwise the coroutine will
234be re-used "as-is": most notably if you change other per-coroutine global
235stuff such as C<$/> you need to revert that change, which is most simply
236done by using local as in C< local $/ >.
222 237
223The pool size is limited to 8 idle coroutines (this can be adjusted by 238The 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 239changing $Coro::POOL_SIZE), and there can be as many non-idle coros as
225required. 240required.
226 241
227If you are concerned about pooled coroutines growing a lot because a 242If 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 { 243single 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. 244{ terminate }> once per second or so to slowly replenish the pool. In
245addition to that, when the stacks used by a handler grows larger than 16kb
246(adjustable with $Coro::POOL_RSS) it will also exit.
230 247
231=cut 248=cut
232 249
233our $POOL_SIZE = 8; 250our $POOL_SIZE = 8;
251our $POOL_RSS = 16 * 1024;
234our @pool; 252our @async_pool;
235 253
236sub pool_handler { 254sub pool_handler {
255 my $cb;
256
237 while () { 257 while () {
238 eval { 258 eval {
239 my ($cb, @arg) = @{ delete $current->{_invoke} or return }; 259 while () {
240 $cb->(@arg); 260 _pool_1 $cb;
261 &$cb;
262 _pool_2 $cb;
263 &schedule;
264 }
241 }; 265 };
266
267 last if $@ eq "\3async_pool terminate\2\n";
242 warn $@ if $@; 268 warn $@ if $@;
243
244 last if @pool >= $POOL_SIZE;
245 push @pool, $current;
246
247 $current->save (Coro::State::SAVE_DEF);
248 $current->prio (0);
249 schedule;
250 } 269 }
251} 270}
252 271
253sub async_pool(&@) { 272sub async_pool(&@) {
254 # this is also inlined into the unlock_scheduler 273 # this is also inlined into the unlock_scheduler
255 my $coro = (pop @pool or new Coro \&pool_handler); 274 my $coro = (pop @async_pool) || new Coro \&pool_handler;
256 275
257 $coro->{_invoke} = [@_]; 276 $coro->{_invoke} = [@_];
258 $coro->ready; 277 $coro->ready;
259 278
260 $coro 279 $coro
278 # wake up sleeping coroutine 297 # wake up sleeping coroutine
279 $current->ready; 298 $current->ready;
280 undef $current; 299 undef $current;
281 }; 300 };
282 301
283 # call schedule until event occured. 302 # call schedule until event occurred.
284 # in case we are woken up for other reasons 303 # in case we are woken up for other reasons
285 # (current still defined), loop. 304 # (current still defined), loop.
286 Coro::schedule while $current; 305 Coro::schedule while $current;
287 } 306 }
288 307
290 309
291"Cede" to other coroutines. This function puts the current coroutine into the 310"Cede" to other coroutines. This function puts the current coroutine into the
292ready queue and calls C<schedule>, which has the effect of giving up the 311ready queue and calls C<schedule>, which has the effect of giving up the
293current "timeslice" to other coroutines of the same or higher priority. 312current "timeslice" to other coroutines of the same or higher priority.
294 313
295Returns true if at least one coroutine switch has happened.
296
297=item Coro::cede_notself 314=item Coro::cede_notself
298 315
299Works like cede, but is not exported by default and will cede to any 316Works like cede, but is not exported by default and will cede to any
300coroutine, regardless of priority, once. 317coroutine, regardless of priority, once.
301 318
302Returns true if at least one coroutine switch has happened.
303
304=item terminate [arg...] 319=item terminate [arg...]
305 320
306Terminates the current coroutine with the given status values (see L<cancel>). 321Terminates the current coroutine with the given status values (see L<cancel>).
322
323=item killall
324
325Kills/terminates/cancels all coroutines except the currently running
326one. This is useful after a fork, either in the child or the parent, as
327usually only one of them should inherit the running coroutines.
307 328
308=cut 329=cut
309 330
310sub terminate { 331sub terminate {
311 $current->cancel (@_); 332 $current->cancel (@_);
333}
334
335sub killall {
336 for (Coro::State::list) {
337 $_->cancel
338 if $_ != $current && UNIVERSAL::isa $_, "Coro";
339 }
312} 340}
313 341
314=back 342=back
315 343
316# dynamic methods 344# dynamic methods
326Create a new coroutine and return it. When the sub returns the coroutine 354Create a new coroutine and return it. When the sub returns the coroutine
327automatically terminates as if C<terminate> with the returned values were 355automatically terminates as if C<terminate> with the returned values were
328called. To make the coroutine run you must first put it into the ready queue 356called. To make the coroutine run you must first put it into the ready queue
329by calling the ready method. 357by calling the ready method.
330 358
331Calling C<exit> in a coroutine will not work correctly, so do not do that. 359See C<async> and C<Coro::State::new> for additional info about the
360coroutine environment.
332 361
333=cut 362=cut
334 363
335sub _run_coro { 364sub _run_coro {
336 terminate &{+shift}; 365 terminate &{+shift};
360 389
361=cut 390=cut
362 391
363sub cancel { 392sub cancel {
364 my $self = shift; 393 my $self = shift;
365 $self->{status} = [@_]; 394 $self->{_status} = [@_];
366 395
367 if ($current == $self) { 396 if ($current == $self) {
368 push @destroy, $self; 397 push @destroy, $self;
369 $manager->ready; 398 $manager->ready;
370 &schedule while 1; 399 &schedule while 1;
374} 403}
375 404
376=item $coroutine->join 405=item $coroutine->join
377 406
378Wait until the coroutine terminates and return any values given to the 407Wait until the coroutine terminates and return any values given to the
379C<terminate> or C<cancel> functions. C<join> can be called multiple times 408C<terminate> or C<cancel> functions. C<join> can be called concurrently
380from multiple coroutine. 409from multiple coroutines.
381 410
382=cut 411=cut
383 412
384sub join { 413sub join {
385 my $self = shift; 414 my $self = shift;
386 415
387 unless ($self->{status}) { 416 unless ($self->{_status}) {
388 my $current = $current; 417 my $current = $current;
389 418
390 push @{$self->{destroy_cb}}, sub { 419 push @{$self->{_on_destroy}}, sub {
391 $current->ready; 420 $current->ready;
392 undef $current; 421 undef $current;
393 }; 422 };
394 423
395 &schedule while $current; 424 &schedule while $current;
396 } 425 }
397 426
398 wantarray ? @{$self->{status}} : $self->{status}[0]; 427 wantarray ? @{$self->{_status}} : $self->{_status}[0];
399} 428}
400 429
401=item $coroutine->on_destroy (\&cb) 430=item $coroutine->on_destroy (\&cb)
402 431
403Registers a callback that is called when this coroutine gets destroyed, 432Registers a callback that is called when this coroutine gets destroyed,
407=cut 436=cut
408 437
409sub on_destroy { 438sub on_destroy {
410 my ($self, $cb) = @_; 439 my ($self, $cb) = @_;
411 440
412 push @{ $self->{destroy_cb} }, $cb; 441 push @{ $self->{_on_destroy} }, $cb;
413} 442}
414 443
415=item $oldprio = $coroutine->prio ($newprio) 444=item $oldprio = $coroutine->prio ($newprio)
416 445
417Sets (or gets, if the argument is missing) the priority of the 446Sets (or gets, if the argument is missing) the priority of the
442=item $olddesc = $coroutine->desc ($newdesc) 471=item $olddesc = $coroutine->desc ($newdesc)
443 472
444Sets (or gets in case the argument is missing) the description for this 473Sets (or gets in case the argument is missing) the description for this
445coroutine. This is just a free-form string you can associate with a coroutine. 474coroutine. This is just a free-form string you can associate with a coroutine.
446 475
476This method simply sets the C<< $coroutine->{desc} >> member to the given string. You
477can modify this member directly if you wish.
478
479=item $coroutine->throw ([$scalar])
480
481If C<$throw> is specified and defined, it will be thrown as an exception
482inside the coroutine at the next convinient point in time (usually after
483it gains control at the next schedule/transfer/cede). Otherwise clears the
484exception object.
485
486The exception object will be thrown "as is" with the specified scalar in
487C<$@>, i.e. if it is a string, no line number or newline will be appended
488(unlike with C<die>).
489
490This can be used as a softer means than C<cancel> to ask a coroutine to
491end itself, although there is no guarentee that the exception will lead to
492termination, and if the exception isn't caught it might well end the whole
493program.
494
447=cut 495=cut
448 496
449sub desc { 497sub desc {
450 my $old = $_[0]{desc}; 498 my $old = $_[0]{desc};
451 $_[0]{desc} = $_[1] if @_ > 1; 499 $_[0]{desc} = $_[1] if @_ > 1;
459=over 4 507=over 4
460 508
461=item Coro::nready 509=item Coro::nready
462 510
463Returns the number of coroutines that are currently in the ready state, 511Returns the number of coroutines that are currently in the ready state,
464i.e. that can be swicthed to. The value C<0> means that the only runnable 512i.e. that can be switched to. The value C<0> means that the only runnable
465coroutine is the currently running one, so C<cede> would have no effect, 513coroutine is the currently running one, so C<cede> would have no effect,
466and C<schedule> would cause a deadlock unless there is an idle handler 514and C<schedule> would cause a deadlock unless there is an idle handler
467that wakes up some coroutines. 515that wakes up some coroutines.
468 516
469=item my $guard = Coro::guard { ... } 517=item my $guard = Coro::guard { ... }
505This utility function takes a BLOCK or code reference and "unblocks" it, 553This utility function takes a BLOCK or code reference and "unblocks" it,
506returning the new coderef. This means that the new coderef will return 554returning the new coderef. This means that the new coderef will return
507immediately without blocking, returning nothing, while the original code 555immediately without blocking, returning nothing, while the original code
508ref will be called (with parameters) from within its own coroutine. 556ref will be called (with parameters) from within its own coroutine.
509 557
510The reason this fucntion exists is that many event libraries (such as the 558The reason this function exists is that many event libraries (such as the
511venerable L<Event|Event> module) are not coroutine-safe (a weaker form 559venerable L<Event|Event> module) are not coroutine-safe (a weaker form
512of thread-safety). This means you must not block within event callbacks, 560of thread-safety). This means you must not block within event callbacks,
513otherwise you might suffer from crashes or worse. 561otherwise you might suffer from crashes or worse.
514 562
515This function allows your callbacks to block by executing them in another 563This function allows your callbacks to block by executing them in another
526 574
527# we create a special coro because we want to cede, 575# we create a special coro because we want to cede,
528# to reduce pressure on the coro pool (because most callbacks 576# to reduce pressure on the coro pool (because most callbacks
529# return immediately and can be reused) and because we cannot cede 577# return immediately and can be reused) and because we cannot cede
530# inside an event callback. 578# inside an event callback.
531our $unblock_scheduler = async { 579our $unblock_scheduler = new Coro sub {
532 while () { 580 while () {
533 while (my $cb = pop @unblock_queue) { 581 while (my $cb = pop @unblock_queue) {
534 # this is an inlined copy of async_pool 582 # this is an inlined copy of async_pool
535 my $coro = (pop @pool or new Coro \&pool_handler); 583 my $coro = (pop @async_pool) || new Coro \&pool_handler;
536 584
537 $coro->{_invoke} = $cb; 585 $coro->{_invoke} = $cb;
538 $coro->ready; 586 $coro->ready;
539 cede; # for short-lived callbacks, this reduces pressure on the coro pool 587 cede; # for short-lived callbacks, this reduces pressure on the coro pool
540 } 588 }
541 schedule; # sleep well 589 schedule; # sleep well
542 } 590 }
543}; 591};
592$unblock_scheduler->desc ("[unblock_sub scheduler]");
544 593
545sub unblock_sub(&) { 594sub unblock_sub(&) {
546 my $cb = shift; 595 my $cb = shift;
547 596
548 sub { 597 sub {
561 610
562 - you must make very sure that no coro is still active on global 611 - you must make very sure that no coro is still active on global
563 destruction. very bad things might happen otherwise (usually segfaults). 612 destruction. very bad things might happen otherwise (usually segfaults).
564 613
565 - this module is not thread-safe. You should only ever use this module 614 - this module is not thread-safe. You should only ever use this module
566 from the same thread (this requirement might be losened in the future 615 from the same thread (this requirement might be loosened in the future
567 to allow per-thread schedulers, but Coro::State does not yet allow 616 to allow per-thread schedulers, but Coro::State does not yet allow
568 this). 617 this).
569 618
570=head1 SEE ALSO 619=head1 SEE ALSO
571 620
621Lower level Configuration, Coroutine Environment: L<Coro::State>.
622
623Debugging: L<Coro::Debug>.
624
572Support/Utility: L<Coro::Cont>, L<Coro::Specific>, L<Coro::State>, L<Coro::Util>. 625Support/Utility: L<Coro::Specific>, L<Coro::Util>.
573 626
574Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>. 627Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>.
575 628
576Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::Select>. 629Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>.
577 630
631Compatibility: L<Coro::LWP>, L<Coro::Storable>, L<Coro::Select>.
632
578Embedding: L<Coro:MakeMaker> 633Embedding: L<Coro::MakeMaker>.
579 634
580=head1 AUTHOR 635=head1 AUTHOR
581 636
582 Marc Lehmann <schmorp@schmorp.de> 637 Marc Lehmann <schmorp@schmorp.de>
583 http://home.schmorp.de/ 638 http://home.schmorp.de/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines