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

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines