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

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines