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.178 by root, Thu Apr 17 22:33:10 2008 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.51';
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
174# static methods. not really.
175 182
176=back 183=back
177 184
178=head2 STATIC METHODS 185=head2 STATIC METHODS
179 186
185 192
186Create a new asynchronous coroutine and return it's coroutine object 193Create a new asynchronous coroutine and return it's coroutine object
187(usually unused). When the sub returns the new coroutine is automatically 194(usually unused). When the sub returns the new coroutine is automatically
188terminated. 195terminated.
189 196
190Calling C<exit> in a coroutine will not work correctly, so do not do that. 197See the C<Coro::State::new> constructor for info about the coroutine
198environment in which coroutines run.
191 199
192When the coroutine dies, the program will exit, just as in the main 200Calling C<exit> in a coroutine will do the same as calling exit outside
193program. 201the coroutine. Likewise, when the coroutine dies, the program will exit,
202just as it would in the main program.
194 203
195 # create a new coroutine that just prints its arguments 204 # create a new coroutine that just prints its arguments
196 async { 205 async {
197 print "@_\n"; 206 print "@_\n";
198 } 1,2,3,4; 207 } 1,2,3,4;
215issued in case of an exception instead of terminating the program, as 224issued 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> 225C<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, 226will not work in the expected way, unless you call terminate or cancel,
218which somehow defeats the purpose of pooling. 227which somehow defeats the purpose of pooling.
219 228
220The priority will be reset to C<0> after each job, otherwise the coroutine 229The priority will be reset to C<0> after each job, tracing will be
221will be re-used "as-is". 230disabled, the description will be reset and the default output filehandle
231gets restored, so you can change alkl these. Otherwise the coroutine will
232be re-used "as-is": most notably if you change other per-coroutine global
233stuff such as C<$/> you need to revert that change, which is most simply
234done by using local as in C< local $/ >.
222 235
223The pool size is limited to 8 idle coroutines (this can be adjusted by 236The 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 237changing $Coro::POOL_SIZE), and there can be as many non-idle coros as
225required. 238required.
226 239
227If you are concerned about pooled coroutines growing a lot because a 240If 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 { 241single 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. 242{ terminate }> once per second or so to slowly replenish the pool. In
243addition to that, when the stacks used by a handler grows larger than 16kb
244(adjustable with $Coro::POOL_RSS) it will also exit.
230 245
231=cut 246=cut
232 247
233our $POOL_SIZE = 8; 248our $POOL_SIZE = 8;
249our $POOL_RSS = 16 * 1024;
234our @pool; 250our @async_pool;
235 251
236sub pool_handler { 252sub pool_handler {
253 my $cb;
254
237 while () { 255 while () {
238 eval { 256 eval {
239 my ($cb, @arg) = @{ delete $current->{_invoke} or return }; 257 while () {
240 $cb->(@arg); 258 _pool_1 $cb;
259 &$cb;
260 _pool_2 $cb;
261 &schedule;
262 }
241 }; 263 };
264
265 last if $@ eq "\3async_pool terminate\2\n";
242 warn $@ if $@; 266 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 } 267 }
251} 268}
252 269
253sub async_pool(&@) { 270sub async_pool(&@) {
254 # this is also inlined into the unlock_scheduler 271 # this is also inlined into the unlock_scheduler
255 my $coro = (pop @pool or new Coro \&pool_handler); 272 my $coro = (pop @async_pool) || new Coro \&pool_handler;
256 273
257 $coro->{_invoke} = [@_]; 274 $coro->{_invoke} = [@_];
258 $coro->ready; 275 $coro->ready;
259 276
260 $coro 277 $coro
278 # wake up sleeping coroutine 295 # wake up sleeping coroutine
279 $current->ready; 296 $current->ready;
280 undef $current; 297 undef $current;
281 }; 298 };
282 299
283 # call schedule until event occured. 300 # call schedule until event occurred.
284 # in case we are woken up for other reasons 301 # in case we are woken up for other reasons
285 # (current still defined), loop. 302 # (current still defined), loop.
286 Coro::schedule while $current; 303 Coro::schedule while $current;
287 } 304 }
288 305
290 307
291"Cede" to other coroutines. This function puts the current coroutine into the 308"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 309ready queue and calls C<schedule>, which has the effect of giving up the
293current "timeslice" to other coroutines of the same or higher priority. 310current "timeslice" to other coroutines of the same or higher priority.
294 311
295Returns true if at least one coroutine switch has happened.
296
297=item Coro::cede_notself 312=item Coro::cede_notself
298 313
299Works like cede, but is not exported by default and will cede to any 314Works like cede, but is not exported by default and will cede to any
300coroutine, regardless of priority, once. 315coroutine, regardless of priority, once.
301 316
302Returns true if at least one coroutine switch has happened.
303
304=item terminate [arg...] 317=item terminate [arg...]
305 318
306Terminates the current coroutine with the given status values (see L<cancel>). 319Terminates the current coroutine with the given status values (see L<cancel>).
320
321=item killall
322
323Kills/terminates/cancels all coroutines except the currently running
324one. This is useful after a fork, either in the child or the parent, as
325usually only one of them should inherit the running coroutines.
307 326
308=cut 327=cut
309 328
310sub terminate { 329sub terminate {
311 $current->cancel (@_); 330 $current->cancel (@_);
312} 331}
313 332
333sub killall {
334 for (Coro::State::list) {
335 $_->cancel
336 if $_ != $current && UNIVERSAL::isa $_, "Coro";
337 }
338}
339
314=back 340=back
315
316# dynamic methods
317 341
318=head2 COROUTINE METHODS 342=head2 COROUTINE METHODS
319 343
320These are the methods you can call on coroutine objects. 344These are the methods you can call on coroutine objects.
321 345
326Create a new coroutine and return it. When the sub returns the coroutine 350Create a new coroutine and return it. When the sub returns the coroutine
327automatically terminates as if C<terminate> with the returned values were 351automatically 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 352called. To make the coroutine run you must first put it into the ready queue
329by calling the ready method. 353by calling the ready method.
330 354
331Calling C<exit> in a coroutine will not work correctly, so do not do that. 355See C<async> and C<Coro::State::new> for additional info about the
356coroutine environment.
332 357
333=cut 358=cut
334 359
335sub _run_coro { 360sub _run_coro {
336 terminate &{+shift}; 361 terminate &{+shift};
360 385
361=cut 386=cut
362 387
363sub cancel { 388sub cancel {
364 my $self = shift; 389 my $self = shift;
365 $self->{status} = [@_]; 390 $self->{_status} = [@_];
366 391
367 if ($current == $self) { 392 if ($current == $self) {
368 push @destroy, $self; 393 push @destroy, $self;
369 $manager->ready; 394 $manager->ready;
370 &schedule while 1; 395 &schedule while 1;
374} 399}
375 400
376=item $coroutine->join 401=item $coroutine->join
377 402
378Wait until the coroutine terminates and return any values given to the 403Wait until the coroutine terminates and return any values given to the
379C<terminate> or C<cancel> functions. C<join> can be called multiple times 404C<terminate> or C<cancel> functions. C<join> can be called concurrently
380from multiple coroutine. 405from multiple coroutines.
381 406
382=cut 407=cut
383 408
384sub join { 409sub join {
385 my $self = shift; 410 my $self = shift;
386 411
387 unless ($self->{status}) { 412 unless ($self->{_status}) {
388 my $current = $current; 413 my $current = $current;
389 414
390 push @{$self->{destroy_cb}}, sub { 415 push @{$self->{_on_destroy}}, sub {
391 $current->ready; 416 $current->ready;
392 undef $current; 417 undef $current;
393 }; 418 };
394 419
395 &schedule while $current; 420 &schedule while $current;
396 } 421 }
397 422
398 wantarray ? @{$self->{status}} : $self->{status}[0]; 423 wantarray ? @{$self->{_status}} : $self->{_status}[0];
399} 424}
400 425
401=item $coroutine->on_destroy (\&cb) 426=item $coroutine->on_destroy (\&cb)
402 427
403Registers a callback that is called when this coroutine gets destroyed, 428Registers a callback that is called when this coroutine gets destroyed,
407=cut 432=cut
408 433
409sub on_destroy { 434sub on_destroy {
410 my ($self, $cb) = @_; 435 my ($self, $cb) = @_;
411 436
412 push @{ $self->{destroy_cb} }, $cb; 437 push @{ $self->{_on_destroy} }, $cb;
413} 438}
414 439
415=item $oldprio = $coroutine->prio ($newprio) 440=item $oldprio = $coroutine->prio ($newprio)
416 441
417Sets (or gets, if the argument is missing) the priority of the 442Sets (or gets, if the argument is missing) the priority of the
442=item $olddesc = $coroutine->desc ($newdesc) 467=item $olddesc = $coroutine->desc ($newdesc)
443 468
444Sets (or gets in case the argument is missing) the description for this 469Sets (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. 470coroutine. This is just a free-form string you can associate with a coroutine.
446 471
472This method simply sets the C<< $coroutine->{desc} >> member to the given string. You
473can modify this member directly if you wish.
474
475=item $coroutine->throw ([$scalar])
476
477If C<$throw> is specified and defined, it will be thrown as an exception
478inside the coroutine at the next convinient point in time (usually after
479it gains control at the next schedule/transfer/cede). Otherwise clears the
480exception object.
481
482The exception object will be thrown "as is" with the specified scalar in
483C<$@>, i.e. if it is a string, no line number or newline will be appended
484(unlike with C<die>).
485
486This can be used as a softer means than C<cancel> to ask a coroutine to
487end itself, although there is no guarentee that the exception will lead to
488termination, and if the exception isn't caught it might well end the whole
489program.
490
447=cut 491=cut
448 492
449sub desc { 493sub desc {
450 my $old = $_[0]{desc}; 494 my $old = $_[0]{desc};
451 $_[0]{desc} = $_[1] if @_ > 1; 495 $_[0]{desc} = $_[1] if @_ > 1;
459=over 4 503=over 4
460 504
461=item Coro::nready 505=item Coro::nready
462 506
463Returns the number of coroutines that are currently in the ready state, 507Returns 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 508i.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, 509coroutine 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 510and C<schedule> would cause a deadlock unless there is an idle handler
467that wakes up some coroutines. 511that wakes up some coroutines.
468 512
469=item my $guard = Coro::guard { ... } 513=item my $guard = Coro::guard { ... }
505This utility function takes a BLOCK or code reference and "unblocks" it, 549This utility function takes a BLOCK or code reference and "unblocks" it,
506returning the new coderef. This means that the new coderef will return 550returning the new coderef. This means that the new coderef will return
507immediately without blocking, returning nothing, while the original code 551immediately without blocking, returning nothing, while the original code
508ref will be called (with parameters) from within its own coroutine. 552ref will be called (with parameters) from within its own coroutine.
509 553
510The reason this fucntion exists is that many event libraries (such as the 554The reason this function exists is that many event libraries (such as the
511venerable L<Event|Event> module) are not coroutine-safe (a weaker form 555venerable L<Event|Event> module) are not coroutine-safe (a weaker form
512of thread-safety). This means you must not block within event callbacks, 556of thread-safety). This means you must not block within event callbacks,
513otherwise you might suffer from crashes or worse. 557otherwise you might suffer from crashes or worse.
514 558
515This function allows your callbacks to block by executing them in another 559This function allows your callbacks to block by executing them in another
526 570
527# we create a special coro because we want to cede, 571# we create a special coro because we want to cede,
528# to reduce pressure on the coro pool (because most callbacks 572# to reduce pressure on the coro pool (because most callbacks
529# return immediately and can be reused) and because we cannot cede 573# return immediately and can be reused) and because we cannot cede
530# inside an event callback. 574# inside an event callback.
531our $unblock_scheduler = async { 575our $unblock_scheduler = new Coro sub {
532 while () { 576 while () {
533 while (my $cb = pop @unblock_queue) { 577 while (my $cb = pop @unblock_queue) {
534 # this is an inlined copy of async_pool 578 # this is an inlined copy of async_pool
535 my $coro = (pop @pool or new Coro \&pool_handler); 579 my $coro = (pop @async_pool) || new Coro \&pool_handler;
536 580
537 $coro->{_invoke} = $cb; 581 $coro->{_invoke} = $cb;
538 $coro->ready; 582 $coro->ready;
539 cede; # for short-lived callbacks, this reduces pressure on the coro pool 583 cede; # for short-lived callbacks, this reduces pressure on the coro pool
540 } 584 }
541 schedule; # sleep well 585 schedule; # sleep well
542 } 586 }
543}; 587};
588$unblock_scheduler->desc ("[unblock_sub scheduler]");
544 589
545sub unblock_sub(&) { 590sub unblock_sub(&) {
546 my $cb = shift; 591 my $cb = shift;
547 592
548 sub { 593 sub {
561 606
562 - you must make very sure that no coro is still active on global 607 - you must make very sure that no coro is still active on global
563 destruction. very bad things might happen otherwise (usually segfaults). 608 destruction. very bad things might happen otherwise (usually segfaults).
564 609
565 - this module is not thread-safe. You should only ever use this module 610 - 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 611 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 612 to allow per-thread schedulers, but Coro::State does not yet allow
568 this). 613 this).
569 614
570=head1 SEE ALSO 615=head1 SEE ALSO
571 616
617Lower level Configuration, Coroutine Environment: L<Coro::State>.
618
619Debugging: L<Coro::Debug>.
620
572Support/Utility: L<Coro::Cont>, L<Coro::Specific>, L<Coro::State>, L<Coro::Util>. 621Support/Utility: L<Coro::Specific>, L<Coro::Util>.
573 622
574Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>. 623Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>.
575 624
576Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::Select>. 625Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>.
577 626
627Compatibility: L<Coro::LWP>, L<Coro::Storable>, L<Coro::Select>.
628
578Embedding: L<Coro:MakeMaker> 629Embedding: L<Coro::MakeMaker>.
579 630
580=head1 AUTHOR 631=head1 AUTHOR
581 632
582 Marc Lehmann <schmorp@schmorp.de> 633 Marc Lehmann <schmorp@schmorp.de>
583 http://home.schmorp.de/ 634 http://home.schmorp.de/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines