1 | =head1 NAME |
1 | =head1 NAME |
2 | |
2 | |
3 | Coro - the real perl threads |
3 | Coro - the only real threads in perl |
4 | |
4 | |
5 | =head1 SYNOPSIS |
5 | =head1 SYNOPSIS |
6 | |
6 | |
7 | use Coro; |
7 | use Coro; |
8 | |
8 | |
… | |
… | |
11 | print "2\n"; |
11 | print "2\n"; |
12 | cede; # yield back to main |
12 | cede; # yield back to main |
13 | print "4\n"; |
13 | print "4\n"; |
14 | }; |
14 | }; |
15 | print "1\n"; |
15 | print "1\n"; |
16 | cede; # yield to coroutine |
16 | cede; # yield to coro |
17 | print "3\n"; |
17 | print "3\n"; |
18 | cede; # and again |
18 | cede; # and again |
19 | |
19 | |
20 | # use locking |
20 | # use locking |
21 | use Coro::Semaphore; |
21 | use Coro::Semaphore; |
… | |
… | |
26 | $locked = 1; |
26 | $locked = 1; |
27 | $lock->up; |
27 | $lock->up; |
28 | |
28 | |
29 | =head1 DESCRIPTION |
29 | =head1 DESCRIPTION |
30 | |
30 | |
31 | This module collection manages coroutines, that is, cooperative |
31 | For a tutorial-style introduction, please read the L<Coro::Intro> |
32 | threads. Coroutines are similar to kernel threads but don't (in general) |
32 | manpage. This manpage mainly contains reference information. |
|
|
33 | |
|
|
34 | This module collection manages continuations in general, most often in |
|
|
35 | the form of cooperative threads (also called coros, or simply "coro" |
|
|
36 | in the documentation). They are similar to kernel threads but don't (in |
33 | run in parallel at the same time even on SMP machines. The specific flavor |
37 | general) run in parallel at the same time even on SMP machines. The |
34 | of coroutine used in this module also guarantees you that it will not |
38 | specific flavor of thread offered by this module also guarantees you that |
35 | switch between coroutines unless necessary, at easily-identified points |
39 | it will not switch between threads unless necessary, at easily-identified |
36 | in your program, so locking and parallel access are rarely an issue, |
40 | points in your program, so locking and parallel access are rarely an |
37 | making coroutine programming much safer and easier than using other thread |
41 | issue, making thread programming much safer and easier than using other |
38 | models. |
42 | thread models. |
39 | |
43 | |
40 | Unlike the so-called "Perl threads" (which are not actually real threads |
44 | Unlike the so-called "Perl threads" (which are not actually real threads |
41 | but only the windows process emulation ported to unix), Coro provides a |
45 | but only the windows process emulation (see section of same name for |
|
|
46 | more details) ported to UNIX, and as such act as processes), Coro |
42 | full shared address space, which makes communication between coroutines |
47 | provides a full shared address space, which makes communication between |
43 | very easy. And coroutines are fast, too: disabling the Windows process |
48 | threads very easy. And coro threads are fast, too: disabling the Windows |
44 | emulation code in your perl and using Coro can easily result in a two to |
49 | process emulation code in your perl and using Coro can easily result in |
45 | four times speed increase for your programs. |
50 | a two to four times speed increase for your programs. A parallel matrix |
|
|
51 | multiplication benchmark (very communication-intensive) runs over 300 |
|
|
52 | times faster on a single core than perls pseudo-threads on a quad core |
|
|
53 | using all four cores. |
46 | |
54 | |
47 | Coro achieves that by supporting multiple running interpreters that share |
55 | Coro achieves that by supporting multiple running interpreters that share |
48 | data, which is especially useful to code pseudo-parallel processes and |
56 | data, which is especially useful to code pseudo-parallel processes and |
49 | for event-based programming, such as multiple HTTP-GET requests running |
57 | for event-based programming, such as multiple HTTP-GET requests running |
50 | concurrently. See L<Coro::AnyEvent> to learn more on how to integrate Coro |
58 | concurrently. See L<Coro::AnyEvent> to learn more on how to integrate Coro |
51 | into an event-based environment. |
59 | into an event-based environment. |
52 | |
60 | |
53 | In this module, a coroutines is defined as "callchain + lexical variables |
61 | In this module, a thread is defined as "callchain + lexical variables + |
54 | + @_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own |
62 | some package variables + C stack), that is, a thread has its own callchain, |
55 | callchain, its own set of lexicals and its own set of perls most important |
63 | its own set of lexicals and its own set of perls most important global |
56 | global variables (see L<Coro::State> for more configuration and background |
64 | variables (see L<Coro::State> for more configuration and background info). |
57 | info). |
|
|
58 | |
65 | |
59 | See also the C<SEE ALSO> section at the end of this document - the Coro |
66 | See also the C<SEE ALSO> section at the end of this document - the Coro |
60 | module family is quite large. |
67 | module family is quite large. |
61 | |
68 | |
|
|
69 | =head1 CORO THREAD LIFE CYCLE |
|
|
70 | |
|
|
71 | During the long and exciting (or not) life of a coro thread, it goes |
|
|
72 | through a number of states: |
|
|
73 | |
|
|
74 | =over 4 |
|
|
75 | |
|
|
76 | =item 1. Creation |
|
|
77 | |
|
|
78 | The first thing in the life of a coro thread is it's creation - |
|
|
79 | obviously. The typical way to create a thread is to call the C<async |
|
|
80 | BLOCK> function: |
|
|
81 | |
|
|
82 | async { |
|
|
83 | # thread code goes here |
|
|
84 | }; |
|
|
85 | |
|
|
86 | You can also pass arguments, which are put in C<@_>: |
|
|
87 | |
|
|
88 | async { |
|
|
89 | print $_[1]; # prints 2 |
|
|
90 | } 1, 2, 3; |
|
|
91 | |
|
|
92 | This creates a new coro thread and puts it into the ready queue, meaning |
|
|
93 | it will run as soon as the CPU is free for it. |
|
|
94 | |
|
|
95 | C<async> will return a coro object - you can store this for future |
|
|
96 | reference or ignore it, the thread itself will keep a reference to it's |
|
|
97 | thread object - threads are alive on their own. |
|
|
98 | |
|
|
99 | Another way to create a thread is to call the C<new> constructor with a |
|
|
100 | code-reference: |
|
|
101 | |
|
|
102 | new Coro sub { |
|
|
103 | # thread code goes here |
|
|
104 | }, @optional_arguments; |
|
|
105 | |
|
|
106 | This is quite similar to calling C<async>, but the important difference is |
|
|
107 | that the new thread is not put into the ready queue, so the thread will |
|
|
108 | not run until somebody puts it there. C<async> is, therefore, identical to |
|
|
109 | this sequence: |
|
|
110 | |
|
|
111 | my $coro = new Coro sub { |
|
|
112 | # thread code goes here |
|
|
113 | }; |
|
|
114 | $coro->ready; |
|
|
115 | return $coro; |
|
|
116 | |
|
|
117 | =item 2. Startup |
|
|
118 | |
|
|
119 | When a new coro thread is created, only a copy of the code reference |
|
|
120 | and the arguments are stored, no extra memory for stacks and so on is |
|
|
121 | allocated, keeping the coro thread in a low-memory state. |
|
|
122 | |
|
|
123 | Only when it actually starts executing will all the resources be finally |
|
|
124 | allocated. |
|
|
125 | |
|
|
126 | The optional arguments specified at coro creation are available in C<@_>, |
|
|
127 | similar to function calls. |
|
|
128 | |
|
|
129 | =item 3. Running / Blocking |
|
|
130 | |
|
|
131 | A lot can happen after the coro thread has started running. Quite usually, |
|
|
132 | it will not run to the end in one go (because you could use a function |
|
|
133 | instead), but it will give up the CPU regularly because it waits for |
|
|
134 | external events. |
|
|
135 | |
|
|
136 | As long as a coro thread runs, it's coro object is available in the global |
|
|
137 | variable C<$Coro::current>. |
|
|
138 | |
|
|
139 | The low-level way to give up the CPU is to call the scheduler, which |
|
|
140 | selects a new coro thread to run: |
|
|
141 | |
|
|
142 | Coro::schedule; |
|
|
143 | |
|
|
144 | Since running threads are not in the ready queue, calling the scheduler |
|
|
145 | without doing anything else will block the coro thread forever - you need |
|
|
146 | to arrange either for the coro to put woken up (readied) by some other |
|
|
147 | event or some other thread, or you can put it into the ready queue before |
|
|
148 | scheduling: |
|
|
149 | |
|
|
150 | # this is exactly what Coro::cede does |
|
|
151 | $Coro::current->ready; |
|
|
152 | Coro::schedule; |
|
|
153 | |
|
|
154 | All the higher-level synchronisation methods (Coro::Semaphore, |
|
|
155 | Coro::rouse_*...) are actually implemented via C<< ->ready >> and C<< |
|
|
156 | Coro::schedule >>. |
|
|
157 | |
|
|
158 | While the coro thread is running it also might get assigned a C-level |
|
|
159 | thread, or the C-level thread might be unassigned from it, as the Coro |
|
|
160 | runtime wishes. A C-level thread needs to be assigned when your perl |
|
|
161 | thread calls into some C-level function and that function in turn calls |
|
|
162 | perl and perl then wants to switch coroutines. This happens most often |
|
|
163 | when you run an event loop and block in the callback, or when perl |
|
|
164 | itself calls some function such as C<AUTOLOAD> or methods via the C<tie> |
|
|
165 | mechanism. |
|
|
166 | |
|
|
167 | =item 4. Termination |
|
|
168 | |
|
|
169 | Many threads actually terminate after some time. There are a number of |
|
|
170 | ways to terminate a coro thread, the simplest is returning from the |
|
|
171 | top-level code reference: |
|
|
172 | |
|
|
173 | async { |
|
|
174 | # after returning from here, the coro thread is terminated |
|
|
175 | }; |
|
|
176 | |
|
|
177 | async { |
|
|
178 | return if 0.5 < rand; # terminate a little earlier, maybe |
|
|
179 | print "got a chance to print this\n"; |
|
|
180 | # or here |
|
|
181 | }; |
|
|
182 | |
|
|
183 | Any values returned from the coroutine can be recovered using C<< ->join |
|
|
184 | >>: |
|
|
185 | |
|
|
186 | my $coro = async { |
|
|
187 | "hello, world\n" # return a string |
|
|
188 | }; |
|
|
189 | |
|
|
190 | my $hello_world = $coro->join; |
|
|
191 | |
|
|
192 | print $hello_world; |
|
|
193 | |
|
|
194 | Another way to terminate is to call C<< Coro::terminate >>, which at any |
|
|
195 | subroutine call nesting level: |
|
|
196 | |
|
|
197 | async { |
|
|
198 | Coro::terminate "return value 1", "return value 2"; |
|
|
199 | }; |
|
|
200 | |
|
|
201 | And yet another way is to C<< ->cancel >> (or C<< ->safe_cancel >>) the |
|
|
202 | coro thread from another thread: |
|
|
203 | |
|
|
204 | my $coro = async { |
|
|
205 | exit 1; |
|
|
206 | }; |
|
|
207 | |
|
|
208 | $coro->cancel; # also accepts values for ->join to retrieve |
|
|
209 | |
|
|
210 | Cancellation I<can> be dangerous - it's a bit like calling C<exit> without |
|
|
211 | actually exiting, and might leave C libraries and XS modules in a weird |
|
|
212 | state. Unlike other thread implementations, however, Coro is exceptionally |
|
|
213 | safe with regards to cancellation, as perl will always be in a consistent |
|
|
214 | state, and for those cases where you want to do truly marvellous things |
|
|
215 | with your coro while it is being cancelled - that is, make sure all |
|
|
216 | cleanup code is executed from the thread being cancelled - there is even a |
|
|
217 | C<< ->safe_cancel >> method. |
|
|
218 | |
|
|
219 | So, cancelling a thread that runs in an XS event loop might not be the |
|
|
220 | best idea, but any other combination that deals with perl only (cancelling |
|
|
221 | when a thread is in a C<tie> method or an C<AUTOLOAD> for example) is |
|
|
222 | safe. |
|
|
223 | |
|
|
224 | =item 5. Cleanup |
|
|
225 | |
|
|
226 | Threads will allocate various resources. Most but not all will be returned |
|
|
227 | when a thread terminates, during clean-up. |
|
|
228 | |
|
|
229 | Cleanup is quite similar to throwing an uncaught exception: perl will |
|
|
230 | work it's way up through all subroutine calls and blocks. On it's way, it |
|
|
231 | will release all C<my> variables, undo all C<local>'s and free any other |
|
|
232 | resources truly local to the thread. |
|
|
233 | |
|
|
234 | So, a common way to free resources is to keep them referenced only by my |
|
|
235 | variables: |
|
|
236 | |
|
|
237 | async { |
|
|
238 | my $big_cache = new Cache ...; |
|
|
239 | }; |
|
|
240 | |
|
|
241 | If there are no other references, then the C<$big_cache> object will be |
|
|
242 | freed when the thread terminates, regardless of how it does so. |
|
|
243 | |
|
|
244 | What it does C<NOT> do is unlock any Coro::Semaphores or similar |
|
|
245 | resources, but that's where the C<guard> methods come in handy: |
|
|
246 | |
|
|
247 | my $sem = new Coro::Semaphore; |
|
|
248 | |
|
|
249 | async { |
|
|
250 | my $lock_guard = $sem->guard; |
|
|
251 | # if we reutrn, or die or get cancelled, here, |
|
|
252 | # then the semaphore will be "up"ed. |
|
|
253 | }; |
|
|
254 | |
|
|
255 | The C<Guard::guard> function comes in handy for any custom cleanup you |
|
|
256 | might want to do: |
|
|
257 | |
|
|
258 | async { |
|
|
259 | my $window = new Gtk2::Window "toplevel"; |
|
|
260 | # The window will not be cleaned up automatically, even when $window |
|
|
261 | # gets freed, so use a guard to ensure it's destruction |
|
|
262 | # in case of an error: |
|
|
263 | my $window_guard = Guard::guard { $window->destroy }; |
|
|
264 | |
|
|
265 | # we are safe here |
|
|
266 | }; |
|
|
267 | |
|
|
268 | Last not least, C<local> can often be handy, too, e.g. when temporarily |
|
|
269 | replacing the coro thread description: |
|
|
270 | |
|
|
271 | sub myfunction { |
|
|
272 | local $Coro::current->{desc} = "inside myfunction(@_)"; |
|
|
273 | |
|
|
274 | # if we return or die here, the description will be restored |
|
|
275 | } |
|
|
276 | |
|
|
277 | =item 6. Viva La Zombie Muerte |
|
|
278 | |
|
|
279 | Even after a thread has terminated and cleaned up it's resources, the coro |
|
|
280 | object still is there and stores the return values of the thread. Only in |
|
|
281 | this state will the coro object be "reference counted" in the normal perl |
|
|
282 | sense: the thread code keeps a reference to it when it is active, but not |
|
|
283 | after it has terminated. |
|
|
284 | |
|
|
285 | The means the coro object gets freed automatically when the thread has |
|
|
286 | terminated and cleaned up and there arenot other references. |
|
|
287 | |
|
|
288 | If there are, the coro object will stay around, and you can call C<< |
|
|
289 | ->join >> as many times as you wish to retrieve the result values: |
|
|
290 | |
|
|
291 | async { |
|
|
292 | print "hi\n"; |
|
|
293 | 1 |
|
|
294 | }; |
|
|
295 | |
|
|
296 | # run the async above, and free everything before returning |
|
|
297 | # from Coro::cede: |
|
|
298 | Coro::cede; |
|
|
299 | |
|
|
300 | { |
|
|
301 | my $coro = async { |
|
|
302 | print "hi\n"; |
|
|
303 | 1 |
|
|
304 | }; |
|
|
305 | |
|
|
306 | # run the async above, and clean up, but do not free the coro |
|
|
307 | # object: |
|
|
308 | Coro::cede; |
|
|
309 | |
|
|
310 | # optionally retrieve the result values |
|
|
311 | my @results = $coro->join; |
|
|
312 | |
|
|
313 | # now $coro goes out of scope, and presumably gets freed |
|
|
314 | }; |
|
|
315 | |
|
|
316 | =back |
|
|
317 | |
62 | =cut |
318 | =cut |
63 | |
319 | |
64 | package Coro; |
320 | package Coro; |
65 | |
321 | |
66 | use strict qw(vars subs); |
322 | use common::sense; |
67 | no warnings "uninitialized"; |
323 | |
|
|
324 | use Carp (); |
|
|
325 | |
|
|
326 | use Guard (); |
68 | |
327 | |
69 | use Coro::State; |
328 | use Coro::State; |
70 | |
329 | |
71 | use base qw(Coro::State Exporter); |
330 | use base qw(Coro::State Exporter); |
72 | |
331 | |
73 | our $idle; # idle handler |
332 | our $idle; # idle handler |
74 | our $main; # main coroutine |
333 | our $main; # main coro |
75 | our $current; # current coroutine |
334 | our $current; # current coro |
76 | |
335 | |
77 | our $VERSION = "5.0"; |
336 | our $VERSION = 5.372; |
78 | |
337 | |
79 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
338 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait); |
80 | our %EXPORT_TAGS = ( |
339 | our %EXPORT_TAGS = ( |
81 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
340 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
82 | ); |
341 | ); |
83 | our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready)); |
342 | our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready)); |
84 | |
343 | |
… | |
… | |
86 | |
345 | |
87 | =over 4 |
346 | =over 4 |
88 | |
347 | |
89 | =item $Coro::main |
348 | =item $Coro::main |
90 | |
349 | |
91 | This variable stores the coroutine object that represents the main |
350 | This variable stores the Coro object that represents the main |
92 | program. While you cna C<ready> it and do most other things you can do to |
351 | program. While you cna C<ready> it and do most other things you can do to |
93 | coroutines, it is mainly useful to compare again C<$Coro::current>, to see |
352 | coro, it is mainly useful to compare again C<$Coro::current>, to see |
94 | whether you are running in the main program or not. |
353 | whether you are running in the main program or not. |
95 | |
354 | |
96 | =cut |
355 | =cut |
97 | |
356 | |
98 | # $main is now being initialised by Coro::State |
357 | # $main is now being initialised by Coro::State |
99 | |
358 | |
100 | =item $Coro::current |
359 | =item $Coro::current |
101 | |
360 | |
102 | The coroutine object representing the current coroutine (the last |
361 | The Coro object representing the current coro (the last |
103 | coroutine that the Coro scheduler switched to). The initial value is |
362 | coro that the Coro scheduler switched to). The initial value is |
104 | C<$Coro::main> (of course). |
363 | C<$Coro::main> (of course). |
105 | |
364 | |
106 | This variable is B<strictly> I<read-only>. You can take copies of the |
365 | This variable is B<strictly> I<read-only>. You can take copies of the |
107 | value stored in it and use it as any other coroutine object, but you must |
366 | value stored in it and use it as any other Coro object, but you must |
108 | not otherwise modify the variable itself. |
367 | not otherwise modify the variable itself. |
109 | |
368 | |
110 | =cut |
369 | =cut |
111 | |
370 | |
112 | sub current() { $current } # [DEPRECATED] |
371 | sub current() { $current } # [DEPRECATED] |
113 | |
372 | |
114 | =item $Coro::idle |
373 | =item $Coro::idle |
115 | |
374 | |
116 | This variable is mainly useful to integrate Coro into event loops. It is |
375 | This variable is mainly useful to integrate Coro into event loops. It is |
117 | usually better to rely on L<Coro::AnyEvent> or LC<Coro::EV>, as this is |
376 | usually better to rely on L<Coro::AnyEvent> or L<Coro::EV>, as this is |
118 | pretty low-level functionality. |
377 | pretty low-level functionality. |
119 | |
378 | |
120 | This variable stores a callback that is called whenever the scheduler |
379 | This variable stores a Coro object that is put into the ready queue when |
121 | finds no ready coroutines to run. The default implementation prints |
380 | there are no other ready threads (without invoking any ready hooks). |
122 | "FATAL: deadlock detected" and exits, because the program has no other way |
|
|
123 | to continue. |
|
|
124 | |
381 | |
|
|
382 | The default implementation dies with "FATAL: deadlock detected.", followed |
|
|
383 | by a thread listing, because the program has no other way to continue. |
|
|
384 | |
125 | This hook is overwritten by modules such as C<Coro::Timer> and |
385 | This hook is overwritten by modules such as C<Coro::EV> and |
126 | C<Coro::AnyEvent> to wait on an external event that hopefully wake up a |
386 | C<Coro::AnyEvent> to wait on an external event that hopefully wakes up a |
127 | coroutine so the scheduler can run it. |
387 | coro so the scheduler can run it. |
128 | |
388 | |
129 | Note that the callback I<must not>, under any circumstances, block |
|
|
130 | the current coroutine. Normally, this is achieved by having an "idle |
|
|
131 | coroutine" that calls the event loop and then blocks again, and then |
|
|
132 | readying that coroutine in the idle handler. |
|
|
133 | |
|
|
134 | See L<Coro::Event> or L<Coro::AnyEvent> for examples of using this |
389 | See L<Coro::EV> or L<Coro::AnyEvent> for examples of using this technique. |
135 | technique. |
|
|
136 | |
390 | |
137 | Please note that if your callback recursively invokes perl (e.g. for event |
|
|
138 | handlers), then it must be prepared to be called recursively itself. |
|
|
139 | |
|
|
140 | =cut |
391 | =cut |
141 | |
392 | |
142 | $idle = sub { |
393 | # ||= because other modules could have provided their own by now |
143 | require Carp; |
394 | $idle ||= new Coro sub { |
144 | Carp::croak ("FATAL: deadlock detected"); |
395 | require Coro::Debug; |
|
|
396 | die "FATAL: deadlock detected.\n" |
|
|
397 | . Coro::Debug::ps_listing (); |
145 | }; |
398 | }; |
146 | |
399 | |
147 | # this coroutine is necessary because a coroutine |
400 | # this coro is necessary because a coro |
148 | # cannot destroy itself. |
401 | # cannot destroy itself. |
149 | our @destroy; |
402 | our @destroy; |
150 | our $manager; |
403 | our $manager; |
151 | |
404 | |
152 | $manager = new Coro sub { |
405 | $manager = new Coro sub { |
153 | while () { |
406 | while () { |
154 | Coro::_cancel shift @destroy |
407 | _destroy shift @destroy |
155 | while @destroy; |
408 | while @destroy; |
156 | |
409 | |
157 | &schedule; |
410 | &schedule; |
158 | } |
411 | } |
159 | }; |
412 | }; |
160 | $manager->{desc} = "[coro manager]"; |
413 | $manager->{desc} = "[coro manager]"; |
161 | $manager->prio (PRIO_MAX); |
414 | $manager->prio (PRIO_MAX); |
162 | |
415 | |
163 | =back |
416 | =back |
164 | |
417 | |
165 | =head1 SIMPLE COROUTINE CREATION |
418 | =head1 SIMPLE CORO CREATION |
166 | |
419 | |
167 | =over 4 |
420 | =over 4 |
168 | |
421 | |
169 | =item async { ... } [@args...] |
422 | =item async { ... } [@args...] |
170 | |
423 | |
171 | Create a new coroutine and return it's coroutine object (usually |
424 | Create a new coro and return its Coro object (usually |
172 | unused). The coroutine will be put into the ready queue, so |
425 | unused). The coro will be put into the ready queue, so |
173 | it will start running automatically on the next scheduler run. |
426 | it will start running automatically on the next scheduler run. |
174 | |
427 | |
175 | The first argument is a codeblock/closure that should be executed in the |
428 | The first argument is a codeblock/closure that should be executed in the |
176 | coroutine. When it returns argument returns the coroutine is automatically |
429 | coro. When it returns argument returns the coro is automatically |
177 | terminated. |
430 | terminated. |
178 | |
431 | |
179 | The remaining arguments are passed as arguments to the closure. |
432 | The remaining arguments are passed as arguments to the closure. |
180 | |
433 | |
181 | See the C<Coro::State::new> constructor for info about the coroutine |
434 | See the C<Coro::State::new> constructor for info about the coro |
182 | environment in which coroutines are executed. |
435 | environment in which coro are executed. |
183 | |
436 | |
184 | Calling C<exit> in a coroutine will do the same as calling exit outside |
437 | Calling C<exit> in a coro will do the same as calling exit outside |
185 | the coroutine. Likewise, when the coroutine dies, the program will exit, |
438 | the coro. Likewise, when the coro dies, the program will exit, |
186 | just as it would in the main program. |
439 | just as it would in the main program. |
187 | |
440 | |
188 | If you do not want that, you can provide a default C<die> handler, or |
441 | If you do not want that, you can provide a default C<die> handler, or |
189 | simply avoid dieing (by use of C<eval>). |
442 | simply avoid dieing (by use of C<eval>). |
190 | |
443 | |
191 | Example: Create a new coroutine that just prints its arguments. |
444 | Example: Create a new coro that just prints its arguments. |
192 | |
445 | |
193 | async { |
446 | async { |
194 | print "@_\n"; |
447 | print "@_\n"; |
195 | } 1,2,3,4; |
448 | } 1,2,3,4; |
196 | |
449 | |
197 | =cut |
|
|
198 | |
|
|
199 | sub async(&@) { |
|
|
200 | my $coro = new Coro @_; |
|
|
201 | $coro->ready; |
|
|
202 | $coro |
|
|
203 | } |
|
|
204 | |
|
|
205 | =item async_pool { ... } [@args...] |
450 | =item async_pool { ... } [@args...] |
206 | |
451 | |
207 | Similar to C<async>, but uses a coroutine pool, so you should not call |
452 | Similar to C<async>, but uses a coro pool, so you should not call |
208 | terminate or join on it (although you are allowed to), and you get a |
453 | terminate or join on it (although you are allowed to), and you get a |
209 | coroutine that might have executed other code already (which can be good |
454 | coro that might have executed other code already (which can be good |
210 | or bad :). |
455 | or bad :). |
211 | |
456 | |
212 | On the plus side, this function is about twice as fast as creating (and |
457 | On the plus side, this function is about twice as fast as creating (and |
213 | destroying) a completely new coroutine, so if you need a lot of generic |
458 | destroying) a completely new coro, so if you need a lot of generic |
214 | coroutines in quick successsion, use C<async_pool>, not C<async>. |
459 | coros in quick successsion, use C<async_pool>, not C<async>. |
215 | |
460 | |
216 | The code block is executed in an C<eval> context and a warning will be |
461 | The code block is executed in an C<eval> context and a warning will be |
217 | issued in case of an exception instead of terminating the program, as |
462 | issued in case of an exception instead of terminating the program, as |
218 | C<async> does. As the coroutine is being reused, stuff like C<on_destroy> |
463 | C<async> does. As the coro is being reused, stuff like C<on_destroy> |
219 | will not work in the expected way, unless you call terminate or cancel, |
464 | will not work in the expected way, unless you call terminate or cancel, |
220 | which somehow defeats the purpose of pooling (but is fine in the |
465 | which somehow defeats the purpose of pooling (but is fine in the |
221 | exceptional case). |
466 | exceptional case). |
222 | |
467 | |
223 | The priority will be reset to C<0> after each run, tracing will be |
468 | The priority will be reset to C<0> after each run, tracing will be |
224 | disabled, the description will be reset and the default output filehandle |
469 | disabled, the description will be reset and the default output filehandle |
225 | gets restored, so you can change all these. Otherwise the coroutine will |
470 | gets restored, so you can change all these. Otherwise the coro will |
226 | be re-used "as-is": most notably if you change other per-coroutine global |
471 | be re-used "as-is": most notably if you change other per-coro global |
227 | stuff such as C<$/> you I<must needs> revert that change, which is most |
472 | stuff such as C<$/> you I<must needs> revert that change, which is most |
228 | simply done by using local as in: C<< local $/ >>. |
473 | simply done by using local as in: C<< local $/ >>. |
229 | |
474 | |
230 | The idle pool size is limited to C<8> idle coroutines (this can be |
475 | The idle pool size is limited to C<8> idle coros (this can be |
231 | adjusted by changing $Coro::POOL_SIZE), but there can be as many non-idle |
476 | adjusted by changing $Coro::POOL_SIZE), but there can be as many non-idle |
232 | coros as required. |
477 | coros as required. |
233 | |
478 | |
234 | If you are concerned about pooled coroutines growing a lot because a |
479 | If you are concerned about pooled coros growing a lot because a |
235 | single C<async_pool> used a lot of stackspace you can e.g. C<async_pool |
480 | single C<async_pool> used a lot of stackspace you can e.g. C<async_pool |
236 | { terminate }> once per second or so to slowly replenish the pool. In |
481 | { terminate }> once per second or so to slowly replenish the pool. In |
237 | addition to that, when the stacks used by a handler grows larger than 32kb |
482 | addition to that, when the stacks used by a handler grows larger than 32kb |
238 | (adjustable via $Coro::POOL_RSS) it will also be destroyed. |
483 | (adjustable via $Coro::POOL_RSS) it will also be destroyed. |
239 | |
484 | |
… | |
… | |
256 | =back |
501 | =back |
257 | |
502 | |
258 | =head1 STATIC METHODS |
503 | =head1 STATIC METHODS |
259 | |
504 | |
260 | Static methods are actually functions that implicitly operate on the |
505 | Static methods are actually functions that implicitly operate on the |
261 | current coroutine. |
506 | current coro. |
262 | |
507 | |
263 | =over 4 |
508 | =over 4 |
264 | |
509 | |
265 | =item schedule |
510 | =item schedule |
266 | |
511 | |
267 | Calls the scheduler. The scheduler will find the next coroutine that is |
512 | Calls the scheduler. The scheduler will find the next coro that is |
268 | to be run from the ready queue and switches to it. The next coroutine |
513 | to be run from the ready queue and switches to it. The next coro |
269 | to be run is simply the one with the highest priority that is longest |
514 | to be run is simply the one with the highest priority that is longest |
270 | in its ready queue. If there is no coroutine ready, it will clal the |
515 | in its ready queue. If there is no coro ready, it will call the |
271 | C<$Coro::idle> hook. |
516 | C<$Coro::idle> hook. |
272 | |
517 | |
273 | Please note that the current coroutine will I<not> be put into the ready |
518 | Please note that the current coro will I<not> be put into the ready |
274 | queue, so calling this function usually means you will never be called |
519 | queue, so calling this function usually means you will never be called |
275 | again unless something else (e.g. an event handler) calls C<< ->ready >>, |
520 | again unless something else (e.g. an event handler) calls C<< ->ready >>, |
276 | thus waking you up. |
521 | thus waking you up. |
277 | |
522 | |
278 | This makes C<schedule> I<the> generic method to use to block the current |
523 | This makes C<schedule> I<the> generic method to use to block the current |
279 | coroutine and wait for events: first you remember the current coroutine in |
524 | coro and wait for events: first you remember the current coro in |
280 | a variable, then arrange for some callback of yours to call C<< ->ready |
525 | a variable, then arrange for some callback of yours to call C<< ->ready |
281 | >> on that once some event happens, and last you call C<schedule> to put |
526 | >> on that once some event happens, and last you call C<schedule> to put |
282 | yourself to sleep. Note that a lot of things can wake your coroutine up, |
527 | yourself to sleep. Note that a lot of things can wake your coro up, |
283 | so you need to check whether the event indeed happened, e.g. by storing the |
528 | so you need to check whether the event indeed happened, e.g. by storing the |
284 | status in a variable. |
529 | status in a variable. |
285 | |
530 | |
286 | See B<HOW TO WAIT FOR A CALLBACK>, below, for some ways to wait for callbacks. |
531 | See B<HOW TO WAIT FOR A CALLBACK>, below, for some ways to wait for callbacks. |
287 | |
532 | |
288 | =item cede |
533 | =item cede |
289 | |
534 | |
290 | "Cede" to other coroutines. This function puts the current coroutine into |
535 | "Cede" to other coros. This function puts the current coro into |
291 | the ready queue and calls C<schedule>, which has the effect of giving |
536 | the ready queue and calls C<schedule>, which has the effect of giving |
292 | up the current "timeslice" to other coroutines of the same or higher |
537 | up the current "timeslice" to other coros of the same or higher |
293 | priority. Once your coroutine gets its turn again it will automatically be |
538 | priority. Once your coro gets its turn again it will automatically be |
294 | resumed. |
539 | resumed. |
295 | |
540 | |
296 | This function is often called C<yield> in other languages. |
541 | This function is often called C<yield> in other languages. |
297 | |
542 | |
298 | =item Coro::cede_notself |
543 | =item Coro::cede_notself |
299 | |
544 | |
300 | Works like cede, but is not exported by default and will cede to I<any> |
545 | Works like cede, but is not exported by default and will cede to I<any> |
301 | coroutine, regardless of priority. This is useful sometimes to ensure |
546 | coro, regardless of priority. This is useful sometimes to ensure |
302 | progress is made. |
547 | progress is made. |
303 | |
548 | |
304 | =item terminate [arg...] |
549 | =item terminate [arg...] |
305 | |
550 | |
306 | Terminates the current coroutine with the given status values (see L<cancel>). |
551 | Terminates the current coro with the given status values (see |
|
|
552 | L<cancel>). The values will not be copied, but referenced directly. |
|
|
553 | |
|
|
554 | =item Coro::on_enter BLOCK, Coro::on_leave BLOCK |
|
|
555 | |
|
|
556 | These function install enter and leave winders in the current scope. The |
|
|
557 | enter block will be executed when on_enter is called and whenever the |
|
|
558 | current coro is re-entered by the scheduler, while the leave block is |
|
|
559 | executed whenever the current coro is blocked by the scheduler, and |
|
|
560 | also when the containing scope is exited (by whatever means, be it exit, |
|
|
561 | die, last etc.). |
|
|
562 | |
|
|
563 | I<Neither invoking the scheduler, nor exceptions, are allowed within those |
|
|
564 | BLOCKs>. That means: do not even think about calling C<die> without an |
|
|
565 | eval, and do not even think of entering the scheduler in any way. |
|
|
566 | |
|
|
567 | Since both BLOCKs are tied to the current scope, they will automatically |
|
|
568 | be removed when the current scope exits. |
|
|
569 | |
|
|
570 | These functions implement the same concept as C<dynamic-wind> in scheme |
|
|
571 | does, and are useful when you want to localise some resource to a specific |
|
|
572 | coro. |
|
|
573 | |
|
|
574 | They slow down thread switching considerably for coros that use them |
|
|
575 | (about 40% for a BLOCK with a single assignment, so thread switching is |
|
|
576 | still reasonably fast if the handlers are fast). |
|
|
577 | |
|
|
578 | These functions are best understood by an example: The following function |
|
|
579 | will change the current timezone to "Antarctica/South_Pole", which |
|
|
580 | requires a call to C<tzset>, but by using C<on_enter> and C<on_leave>, |
|
|
581 | which remember/change the current timezone and restore the previous |
|
|
582 | value, respectively, the timezone is only changed for the coro that |
|
|
583 | installed those handlers. |
|
|
584 | |
|
|
585 | use POSIX qw(tzset); |
|
|
586 | |
|
|
587 | async { |
|
|
588 | my $old_tz; # store outside TZ value here |
|
|
589 | |
|
|
590 | Coro::on_enter { |
|
|
591 | $old_tz = $ENV{TZ}; # remember the old value |
|
|
592 | |
|
|
593 | $ENV{TZ} = "Antarctica/South_Pole"; |
|
|
594 | tzset; # enable new value |
|
|
595 | }; |
|
|
596 | |
|
|
597 | Coro::on_leave { |
|
|
598 | $ENV{TZ} = $old_tz; |
|
|
599 | tzset; # restore old value |
|
|
600 | }; |
|
|
601 | |
|
|
602 | # at this place, the timezone is Antarctica/South_Pole, |
|
|
603 | # without disturbing the TZ of any other coro. |
|
|
604 | }; |
|
|
605 | |
|
|
606 | This can be used to localise about any resource (locale, uid, current |
|
|
607 | working directory etc.) to a block, despite the existance of other |
|
|
608 | coros. |
|
|
609 | |
|
|
610 | Another interesting example implements time-sliced multitasking using |
|
|
611 | interval timers (this could obviously be optimised, but does the job): |
|
|
612 | |
|
|
613 | # "timeslice" the given block |
|
|
614 | sub timeslice(&) { |
|
|
615 | use Time::HiRes (); |
|
|
616 | |
|
|
617 | Coro::on_enter { |
|
|
618 | # on entering the thread, we set an VTALRM handler to cede |
|
|
619 | $SIG{VTALRM} = sub { cede }; |
|
|
620 | # and then start the interval timer |
|
|
621 | Time::HiRes::setitimer &Time::HiRes::ITIMER_VIRTUAL, 0.01, 0.01; |
|
|
622 | }; |
|
|
623 | Coro::on_leave { |
|
|
624 | # on leaving the thread, we stop the interval timer again |
|
|
625 | Time::HiRes::setitimer &Time::HiRes::ITIMER_VIRTUAL, 0, 0; |
|
|
626 | }; |
|
|
627 | |
|
|
628 | &{+shift}; |
|
|
629 | } |
|
|
630 | |
|
|
631 | # use like this: |
|
|
632 | timeslice { |
|
|
633 | # The following is an endless loop that would normally |
|
|
634 | # monopolise the process. Since it runs in a timesliced |
|
|
635 | # environment, it will regularly cede to other threads. |
|
|
636 | while () { } |
|
|
637 | }; |
|
|
638 | |
307 | |
639 | |
308 | =item killall |
640 | =item killall |
309 | |
641 | |
310 | Kills/terminates/cancels all coroutines except the currently running |
642 | Kills/terminates/cancels all coros except the currently running one. |
311 | one. This is useful after a fork, either in the child or the parent, as |
|
|
312 | usually only one of them should inherit the running coroutines. |
|
|
313 | |
643 | |
314 | Note that while this will try to free some of the main programs resources, |
644 | Note that while this will try to free some of the main interpreter |
|
|
645 | resources if the calling coro isn't the main coro, but one |
315 | you cannot free all of them, so if a coroutine that is not the main |
646 | cannot free all of them, so if a coro that is not the main coro |
316 | program calls this function, there will be some one-time resource leak. |
647 | calls this function, there will be some one-time resource leak. |
317 | |
648 | |
318 | =cut |
649 | =cut |
319 | |
650 | |
320 | sub killall { |
651 | sub killall { |
321 | for (Coro::State::list) { |
652 | for (Coro::State::list) { |
… | |
… | |
324 | } |
655 | } |
325 | } |
656 | } |
326 | |
657 | |
327 | =back |
658 | =back |
328 | |
659 | |
329 | =head1 COROUTINE OBJECT METHODS |
660 | =head1 CORO OBJECT METHODS |
330 | |
661 | |
331 | These are the methods you can call on coroutine objects (or to create |
662 | These are the methods you can call on coro objects (or to create |
332 | them). |
663 | them). |
333 | |
664 | |
334 | =over 4 |
665 | =over 4 |
335 | |
666 | |
336 | =item new Coro \&sub [, @args...] |
667 | =item new Coro \&sub [, @args...] |
337 | |
668 | |
338 | Create a new coroutine and return it. When the sub returns, the coroutine |
669 | Create a new coro and return it. When the sub returns, the coro |
339 | automatically terminates as if C<terminate> with the returned values were |
670 | automatically terminates as if C<terminate> with the returned values were |
340 | called. To make the coroutine run you must first put it into the ready |
671 | called. To make the coro run you must first put it into the ready |
341 | queue by calling the ready method. |
672 | queue by calling the ready method. |
342 | |
673 | |
343 | See C<async> and C<Coro::State::new> for additional info about the |
674 | See C<async> and C<Coro::State::new> for additional info about the |
344 | coroutine environment. |
675 | coro environment. |
345 | |
676 | |
346 | =cut |
677 | =cut |
347 | |
678 | |
348 | sub _terminate { |
679 | sub _coro_run { |
349 | terminate &{+shift}; |
680 | terminate &{+shift}; |
350 | } |
681 | } |
351 | |
682 | |
352 | =item $success = $coroutine->ready |
683 | =item $success = $coro->ready |
353 | |
684 | |
354 | Put the given coroutine into the end of its ready queue (there is one |
685 | Put the given coro into the end of its ready queue (there is one |
355 | queue for each priority) and return true. If the coroutine is already in |
686 | queue for each priority) and return true. If the coro is already in |
356 | the ready queue, do nothing and return false. |
687 | the ready queue, do nothing and return false. |
357 | |
688 | |
358 | This ensures that the scheduler will resume this coroutine automatically |
689 | This ensures that the scheduler will resume this coro automatically |
359 | once all the coroutines of higher priority and all coroutines of the same |
690 | once all the coro of higher priority and all coro of the same |
360 | priority that were put into the ready queue earlier have been resumed. |
691 | priority that were put into the ready queue earlier have been resumed. |
361 | |
692 | |
|
|
693 | =item $coro->suspend |
|
|
694 | |
|
|
695 | Suspends the specified coro. A suspended coro works just like any other |
|
|
696 | coro, except that the scheduler will not select a suspended coro for |
|
|
697 | execution. |
|
|
698 | |
|
|
699 | Suspending a coro can be useful when you want to keep the coro from |
|
|
700 | running, but you don't want to destroy it, or when you want to temporarily |
|
|
701 | freeze a coro (e.g. for debugging) to resume it later. |
|
|
702 | |
|
|
703 | A scenario for the former would be to suspend all (other) coros after a |
|
|
704 | fork and keep them alive, so their destructors aren't called, but new |
|
|
705 | coros can be created. |
|
|
706 | |
|
|
707 | =item $coro->resume |
|
|
708 | |
|
|
709 | If the specified coro was suspended, it will be resumed. Note that when |
|
|
710 | the coro was in the ready queue when it was suspended, it might have been |
|
|
711 | unreadied by the scheduler, so an activation might have been lost. |
|
|
712 | |
|
|
713 | To avoid this, it is best to put a suspended coro into the ready queue |
|
|
714 | unconditionally, as every synchronisation mechanism must protect itself |
|
|
715 | against spurious wakeups, and the one in the Coro family certainly do |
|
|
716 | that. |
|
|
717 | |
362 | =item $is_ready = $coroutine->is_ready |
718 | =item $is_ready = $coro->is_ready |
363 | |
719 | |
364 | Return whether the coroutine is currently the ready queue or not, |
720 | Returns true iff the Coro object is in the ready queue. Unless the Coro |
|
|
721 | object gets destroyed, it will eventually be scheduled by the scheduler. |
365 | |
722 | |
|
|
723 | =item $is_running = $coro->is_running |
|
|
724 | |
|
|
725 | Returns true iff the Coro object is currently running. Only one Coro object |
|
|
726 | can ever be in the running state (but it currently is possible to have |
|
|
727 | multiple running Coro::States). |
|
|
728 | |
|
|
729 | =item $is_suspended = $coro->is_suspended |
|
|
730 | |
|
|
731 | Returns true iff this Coro object has been suspended. Suspended Coros will |
|
|
732 | not ever be scheduled. |
|
|
733 | |
366 | =item $coroutine->cancel (arg...) |
734 | =item $coro->cancel (arg...) |
367 | |
735 | |
368 | Terminates the given coroutine and makes it return the given arguments as |
736 | Terminates the given Coro thread and makes it return the given arguments as |
369 | status (default: the empty list). Never returns if the coroutine is the |
737 | status (default: an empty list). Never returns if the Coro is the |
370 | current coroutine. |
738 | current Coro. |
371 | |
739 | |
372 | =cut |
740 | This is a rather brutal way to free a coro, with some limitations - if |
|
|
741 | the thread is inside a C callback that doesn't expect to be canceled, |
|
|
742 | bad things can happen, or if the cancelled thread insists on running |
|
|
743 | complicated cleanup handlers that rely on it'S thread context, things will |
|
|
744 | not work. |
373 | |
745 | |
374 | sub cancel { |
746 | Any cleanup code being run (e.g. from C<guard> blocks) will be run without |
375 | my $self = shift; |
747 | a thread context, and is not allowed to switch to other threads. On the |
|
|
748 | plus side, C<< ->cancel >> will always clean up the thread, no matter |
|
|
749 | what. If your cleanup code is complex or you want to avoid cancelling a |
|
|
750 | C-thread that doesn't know how to clean up itself, it can be better to C<< |
|
|
751 | ->throw >> an exception, or use C<< ->safe_cancel >>. |
376 | |
752 | |
377 | if ($current == $self) { |
753 | The arguments to C<< ->cancel >> are not copied, but instead will |
378 | terminate @_; |
754 | be referenced directly (e.g. if you pass C<$var> and after the call |
379 | } else { |
755 | change that variable, then you might change the return values passed to |
380 | $self->{_status} = [@_]; |
756 | e.g. C<join>, so don't do that). |
381 | $self->_cancel; |
757 | |
|
|
758 | The resources of the Coro are usually freed (or destructed) before this |
|
|
759 | call returns, but this can be delayed for an indefinite amount of time, as |
|
|
760 | in some cases the manager thread has to run first to actually destruct the |
|
|
761 | Coro object. |
|
|
762 | |
|
|
763 | =item $coro->safe_cancel ($arg...) |
|
|
764 | |
|
|
765 | Works mostly like C<< ->cancel >>, but is inherently "safer", and |
|
|
766 | consequently, can fail with an exception in cases the thread is not in a |
|
|
767 | cancellable state. |
|
|
768 | |
|
|
769 | This method works a bit like throwing an exception that cannot be caught |
|
|
770 | - specifically, it will clean up the thread from within itself, so |
|
|
771 | all cleanup handlers (e.g. C<guard> blocks) are run with full thread |
|
|
772 | context and can block if they wish. The downside is that there is no |
|
|
773 | guarantee that the thread can be cancelled when you call this method, and |
|
|
774 | therefore, it might fail. It is also considerably slower than C<cancel> or |
|
|
775 | C<terminate>. |
|
|
776 | |
|
|
777 | A thread is in a safe-cancellable state if it either hasn't been run yet, |
|
|
778 | or it has no C context attached and is inside an SLF function. |
|
|
779 | |
|
|
780 | The latter two basically mean that the thread isn't currently inside a |
|
|
781 | perl callback called from some C function (usually via some XS modules) |
|
|
782 | and isn't currently executing inside some C function itself (via Coro's XS |
|
|
783 | API). |
|
|
784 | |
|
|
785 | This call returns true when it could cancel the thread, or croaks with an |
|
|
786 | error otherwise (i.e. it either returns true or doesn't return at all). |
|
|
787 | |
|
|
788 | Why the weird interface? Well, there are two common models on how and |
|
|
789 | when to cancel things. In the first, you have the expectation that your |
|
|
790 | coro thread can be cancelled when you want to cancel it - if the thread |
|
|
791 | isn't cancellable, this would be a bug somewhere, so C<< ->safe_cancel >> |
|
|
792 | croaks to notify of the bug. |
|
|
793 | |
|
|
794 | In the second model you sometimes want to ask nicely to cancel a thread, |
|
|
795 | but if it's not a good time, well, then don't cancel. This can be done |
|
|
796 | relatively easy like this: |
|
|
797 | |
|
|
798 | if (! eval { $coro->safe_cancel }) { |
|
|
799 | warn "unable to cancel thread: $@"; |
382 | } |
800 | } |
383 | } |
|
|
384 | |
801 | |
|
|
802 | However, what you never should do is first try to cancel "safely" and |
|
|
803 | if that fails, cancel the "hard" way with C<< ->cancel >>. That makes |
|
|
804 | no sense: either you rely on being able to execute cleanup code in your |
|
|
805 | thread context, or you don't. If you do, then C<< ->safe_cancel >> is the |
|
|
806 | only way, and if you don't, then C<< ->cancel >> is always faster and more |
|
|
807 | direct. |
|
|
808 | |
385 | =item $coroutine->schedule_to |
809 | =item $coro->schedule_to |
386 | |
810 | |
387 | Puts the current coroutine to sleep (like C<Coro::schedule>), but instead |
811 | Puts the current coro to sleep (like C<Coro::schedule>), but instead |
388 | of continuing with the next coro from the ready queue, always switch to |
812 | of continuing with the next coro from the ready queue, always switch to |
389 | the given coroutine object (regardless of priority etc.). The readyness |
813 | the given coro object (regardless of priority etc.). The readyness |
390 | state of that coroutine isn't changed. |
814 | state of that coro isn't changed. |
391 | |
815 | |
392 | This is an advanced method for special cases - I'd love to hear about any |
816 | This is an advanced method for special cases - I'd love to hear about any |
393 | uses for this one. |
817 | uses for this one. |
394 | |
818 | |
395 | =item $coroutine->cede_to |
819 | =item $coro->cede_to |
396 | |
820 | |
397 | Like C<schedule_to>, but puts the current coroutine into the ready |
821 | Like C<schedule_to>, but puts the current coro into the ready |
398 | queue. This has the effect of temporarily switching to the given |
822 | queue. This has the effect of temporarily switching to the given |
399 | coroutine, and continuing some time later. |
823 | coro, and continuing some time later. |
400 | |
824 | |
401 | This is an advanced method for special cases - I'd love to hear about any |
825 | This is an advanced method for special cases - I'd love to hear about any |
402 | uses for this one. |
826 | uses for this one. |
403 | |
827 | |
404 | =item $coroutine->throw ([$scalar]) |
828 | =item $coro->throw ([$scalar]) |
405 | |
829 | |
406 | If C<$throw> is specified and defined, it will be thrown as an exception |
830 | If C<$throw> is specified and defined, it will be thrown as an exception |
407 | inside the coroutine at the next convenient point in time. Otherwise |
831 | inside the coro at the next convenient point in time. Otherwise |
408 | clears the exception object. |
832 | clears the exception object. |
409 | |
833 | |
410 | Coro will check for the exception each time a schedule-like-function |
834 | Coro will check for the exception each time a schedule-like-function |
411 | returns, i.e. after each C<schedule>, C<cede>, C<< Coro::Semaphore->down |
835 | returns, i.e. after each C<schedule>, C<cede>, C<< Coro::Semaphore->down |
412 | >>, C<< Coro::Handle->readable >> and so on. Most of these functions |
836 | >>, C<< Coro::Handle->readable >> and so on. Most of those functions (all |
413 | detect this case and return early in case an exception is pending. |
837 | that are part of Coro itself) detect this case and return early in case an |
|
|
838 | exception is pending. |
414 | |
839 | |
415 | The exception object will be thrown "as is" with the specified scalar in |
840 | The exception object will be thrown "as is" with the specified scalar in |
416 | C<$@>, i.e. if it is a string, no line number or newline will be appended |
841 | C<$@>, i.e. if it is a string, no line number or newline will be appended |
417 | (unlike with C<die>). |
842 | (unlike with C<die>). |
418 | |
843 | |
419 | This can be used as a softer means than C<cancel> to ask a coroutine to |
844 | This can be used as a softer means than either C<cancel> or C<safe_cancel |
420 | end itself, although there is no guarantee that the exception will lead to |
845 | >to ask a coro to end itself, although there is no guarantee that the |
421 | termination, and if the exception isn't caught it might well end the whole |
846 | exception will lead to termination, and if the exception isn't caught it |
422 | program. |
847 | might well end the whole program. |
423 | |
848 | |
424 | You might also think of C<throw> as being the moral equivalent of |
849 | You might also think of C<throw> as being the moral equivalent of |
425 | C<kill>ing a coroutine with a signal (in this case, a scalar). |
850 | C<kill>ing a coro with a signal (in this case, a scalar). |
426 | |
851 | |
427 | =item $coroutine->join |
852 | =item $coro->join |
428 | |
853 | |
429 | Wait until the coroutine terminates and return any values given to the |
854 | Wait until the coro terminates and return any values given to the |
430 | C<terminate> or C<cancel> functions. C<join> can be called concurrently |
855 | C<terminate> or C<cancel> functions. C<join> can be called concurrently |
431 | from multiple coroutines, and all will be resumed and given the status |
856 | from multiple threads, and all will be resumed and given the status |
432 | return once the C<$coroutine> terminates. |
857 | return once the C<$coro> terminates. |
433 | |
858 | |
434 | =cut |
859 | =cut |
435 | |
860 | |
436 | sub join { |
861 | sub join { |
437 | my $self = shift; |
862 | my $self = shift; |
… | |
… | |
445 | }; |
870 | }; |
446 | |
871 | |
447 | &schedule while $current; |
872 | &schedule while $current; |
448 | } |
873 | } |
449 | |
874 | |
450 | wantarray ? @{$self->{_status}} : $self->{_status}[0]; |
875 | wantarray ? @{$self->{_status}} : $self->{_status}[0] |
451 | } |
876 | } |
452 | |
877 | |
453 | =item $coroutine->on_destroy (\&cb) |
878 | =item $coro->on_destroy (\&cb) |
454 | |
879 | |
455 | Registers a callback that is called when this coroutine gets destroyed, |
880 | Registers a callback that is called when this coro thread gets destroyed, |
456 | but before it is joined. The callback gets passed the terminate arguments, |
881 | that is, after it's resources have been freed but before it is joined. The |
|
|
882 | callback gets passed the terminate/cancel arguments, if any, and I<must |
457 | if any, and I<must not> die, under any circumstances. |
883 | not> die, under any circumstances. |
|
|
884 | |
|
|
885 | There can be any number of C<on_destroy> callbacks per coro, and there is |
|
|
886 | no way currently to remove a callback once added. |
458 | |
887 | |
459 | =cut |
888 | =cut |
460 | |
889 | |
461 | sub on_destroy { |
890 | sub on_destroy { |
462 | my ($self, $cb) = @_; |
891 | my ($self, $cb) = @_; |
463 | |
892 | |
464 | push @{ $self->{_on_destroy} }, $cb; |
893 | push @{ $self->{_on_destroy} }, $cb; |
465 | } |
894 | } |
466 | |
895 | |
467 | =item $oldprio = $coroutine->prio ($newprio) |
896 | =item $oldprio = $coro->prio ($newprio) |
468 | |
897 | |
469 | Sets (or gets, if the argument is missing) the priority of the |
898 | Sets (or gets, if the argument is missing) the priority of the |
470 | coroutine. Higher priority coroutines get run before lower priority |
899 | coro thread. Higher priority coro get run before lower priority |
471 | coroutines. Priorities are small signed integers (currently -4 .. +3), |
900 | coros. Priorities are small signed integers (currently -4 .. +3), |
472 | that you can refer to using PRIO_xxx constants (use the import tag :prio |
901 | that you can refer to using PRIO_xxx constants (use the import tag :prio |
473 | to get then): |
902 | to get then): |
474 | |
903 | |
475 | PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN |
904 | PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN |
476 | 3 > 1 > 0 > -1 > -3 > -4 |
905 | 3 > 1 > 0 > -1 > -3 > -4 |
477 | |
906 | |
478 | # set priority to HIGH |
907 | # set priority to HIGH |
479 | current->prio(PRIO_HIGH); |
908 | current->prio (PRIO_HIGH); |
480 | |
909 | |
481 | The idle coroutine ($Coro::idle) always has a lower priority than any |
910 | The idle coro thread ($Coro::idle) always has a lower priority than any |
482 | existing coroutine. |
911 | existing coro. |
483 | |
912 | |
484 | Changing the priority of the current coroutine will take effect immediately, |
913 | Changing the priority of the current coro will take effect immediately, |
485 | but changing the priority of coroutines in the ready queue (but not |
914 | but changing the priority of a coro in the ready queue (but not running) |
486 | running) will only take effect after the next schedule (of that |
915 | will only take effect after the next schedule (of that coro). This is a |
487 | coroutine). This is a bug that will be fixed in some future version. |
916 | bug that will be fixed in some future version. |
488 | |
917 | |
489 | =item $newprio = $coroutine->nice ($change) |
918 | =item $newprio = $coro->nice ($change) |
490 | |
919 | |
491 | Similar to C<prio>, but subtract the given value from the priority (i.e. |
920 | Similar to C<prio>, but subtract the given value from the priority (i.e. |
492 | higher values mean lower priority, just as in unix). |
921 | higher values mean lower priority, just as in UNIX's nice command). |
493 | |
922 | |
494 | =item $olddesc = $coroutine->desc ($newdesc) |
923 | =item $olddesc = $coro->desc ($newdesc) |
495 | |
924 | |
496 | Sets (or gets in case the argument is missing) the description for this |
925 | Sets (or gets in case the argument is missing) the description for this |
497 | coroutine. This is just a free-form string you can associate with a |
926 | coro thread. This is just a free-form string you can associate with a |
498 | coroutine. |
927 | coro. |
499 | |
928 | |
500 | This method simply sets the C<< $coroutine->{desc} >> member to the given |
929 | This method simply sets the C<< $coro->{desc} >> member to the given |
501 | string. You can modify this member directly if you wish. |
930 | string. You can modify this member directly if you wish, and in fact, this |
|
|
931 | is often preferred to indicate major processing states that cna then be |
|
|
932 | seen for example in a L<Coro::Debug> session: |
|
|
933 | |
|
|
934 | sub my_long_function { |
|
|
935 | local $Coro::current->{desc} = "now in my_long_function"; |
|
|
936 | ... |
|
|
937 | $Coro::current->{desc} = "my_long_function: phase 1"; |
|
|
938 | ... |
|
|
939 | $Coro::current->{desc} = "my_long_function: phase 2"; |
|
|
940 | ... |
|
|
941 | } |
502 | |
942 | |
503 | =cut |
943 | =cut |
504 | |
944 | |
505 | sub desc { |
945 | sub desc { |
506 | my $old = $_[0]{desc}; |
946 | my $old = $_[0]{desc}; |
… | |
… | |
519 | |
959 | |
520 | =over 4 |
960 | =over 4 |
521 | |
961 | |
522 | =item Coro::nready |
962 | =item Coro::nready |
523 | |
963 | |
524 | Returns the number of coroutines that are currently in the ready state, |
964 | Returns the number of coro that are currently in the ready state, |
525 | i.e. that can be switched to by calling C<schedule> directory or |
965 | i.e. that can be switched to by calling C<schedule> directory or |
526 | indirectly. The value C<0> means that the only runnable coroutine is the |
966 | indirectly. The value C<0> means that the only runnable coro is the |
527 | currently running one, so C<cede> would have no effect, and C<schedule> |
967 | currently running one, so C<cede> would have no effect, and C<schedule> |
528 | would cause a deadlock unless there is an idle handler that wakes up some |
968 | would cause a deadlock unless there is an idle handler that wakes up some |
529 | coroutines. |
969 | coro. |
530 | |
970 | |
531 | =item my $guard = Coro::guard { ... } |
971 | =item my $guard = Coro::guard { ... } |
532 | |
972 | |
533 | This creates and returns a guard object. Nothing happens until the object |
973 | This function still exists, but is deprecated. Please use the |
534 | gets destroyed, in which case the codeblock given as argument will be |
974 | C<Guard::guard> function instead. |
535 | executed. This is useful to free locks or other resources in case of a |
|
|
536 | runtime error or when the coroutine gets canceled, as in both cases the |
|
|
537 | guard block will be executed. The guard object supports only one method, |
|
|
538 | C<< ->cancel >>, which will keep the codeblock from being executed. |
|
|
539 | |
975 | |
540 | Example: set some flag and clear it again when the coroutine gets canceled |
|
|
541 | or the function returns: |
|
|
542 | |
|
|
543 | sub do_something { |
|
|
544 | my $guard = Coro::guard { $busy = 0 }; |
|
|
545 | $busy = 1; |
|
|
546 | |
|
|
547 | # do something that requires $busy to be true |
|
|
548 | } |
|
|
549 | |
|
|
550 | =cut |
976 | =cut |
551 | |
977 | |
552 | sub guard(&) { |
978 | BEGIN { *guard = \&Guard::guard } |
553 | bless \(my $cb = $_[0]), "Coro::guard" |
|
|
554 | } |
|
|
555 | |
|
|
556 | sub Coro::guard::cancel { |
|
|
557 | ${$_[0]} = sub { }; |
|
|
558 | } |
|
|
559 | |
|
|
560 | sub Coro::guard::DESTROY { |
|
|
561 | ${$_[0]}->(); |
|
|
562 | } |
|
|
563 | |
|
|
564 | |
979 | |
565 | =item unblock_sub { ... } |
980 | =item unblock_sub { ... } |
566 | |
981 | |
567 | This utility function takes a BLOCK or code reference and "unblocks" it, |
982 | This utility function takes a BLOCK or code reference and "unblocks" it, |
568 | returning a new coderef. Unblocking means that calling the new coderef |
983 | returning a new coderef. Unblocking means that calling the new coderef |
569 | will return immediately without blocking, returning nothing, while the |
984 | will return immediately without blocking, returning nothing, while the |
570 | original code ref will be called (with parameters) from within another |
985 | original code ref will be called (with parameters) from within another |
571 | coroutine. |
986 | coro. |
572 | |
987 | |
573 | The reason this function exists is that many event libraries (such as the |
988 | The reason this function exists is that many event libraries (such as |
574 | venerable L<Event|Event> module) are not coroutine-safe (a weaker form |
989 | the venerable L<Event|Event> module) are not thread-safe (a weaker form |
575 | of thread-safety). This means you must not block within event callbacks, |
990 | of reentrancy). This means you must not block within event callbacks, |
576 | otherwise you might suffer from crashes or worse. The only event library |
991 | otherwise you might suffer from crashes or worse. The only event library |
577 | currently known that is safe to use without C<unblock_sub> is L<EV>. |
992 | currently known that is safe to use without C<unblock_sub> is L<EV> (but |
|
|
993 | you might still run into deadlocks if all event loops are blocked). |
|
|
994 | |
|
|
995 | Coro will try to catch you when you block in the event loop |
|
|
996 | ("FATAL:$Coro::IDLE blocked itself"), but this is just best effort and |
|
|
997 | only works when you do not run your own event loop. |
578 | |
998 | |
579 | This function allows your callbacks to block by executing them in another |
999 | This function allows your callbacks to block by executing them in another |
580 | coroutine where it is safe to block. One example where blocking is handy |
1000 | coro where it is safe to block. One example where blocking is handy |
581 | is when you use the L<Coro::AIO|Coro::AIO> functions to save results to |
1001 | is when you use the L<Coro::AIO|Coro::AIO> functions to save results to |
582 | disk, for example. |
1002 | disk, for example. |
583 | |
1003 | |
584 | In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when |
1004 | In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when |
585 | creating event callbacks that want to block. |
1005 | creating event callbacks that want to block. |
586 | |
1006 | |
587 | If your handler does not plan to block (e.g. simply sends a message to |
1007 | If your handler does not plan to block (e.g. simply sends a message to |
588 | another coroutine, or puts some other coroutine into the ready queue), |
1008 | another coro, or puts some other coro into the ready queue), there is |
589 | there is no reason to use C<unblock_sub>. |
1009 | no reason to use C<unblock_sub>. |
590 | |
1010 | |
591 | Note that you also need to use C<unblock_sub> for any other callbacks that |
1011 | Note that you also need to use C<unblock_sub> for any other callbacks that |
592 | are indirectly executed by any C-based event loop. For example, when you |
1012 | are indirectly executed by any C-based event loop. For example, when you |
593 | use a module that uses L<AnyEvent> (and you use L<Coro::AnyEvent>) and it |
1013 | use a module that uses L<AnyEvent> (and you use L<Coro::AnyEvent>) and it |
594 | provides callbacks that are the result of some event callback, then you |
1014 | provides callbacks that are the result of some event callback, then you |
… | |
… | |
624 | unshift @unblock_queue, [$cb, @_]; |
1044 | unshift @unblock_queue, [$cb, @_]; |
625 | $unblock_scheduler->ready; |
1045 | $unblock_scheduler->ready; |
626 | } |
1046 | } |
627 | } |
1047 | } |
628 | |
1048 | |
629 | =item $cb = Coro::rouse_cb |
1049 | =item $cb = rouse_cb |
630 | |
1050 | |
631 | Create and return a "rouse callback". That's a code reference that, when |
1051 | Create and return a "rouse callback". That's a code reference that, |
632 | called, will save its arguments and notify the owner coroutine of the |
1052 | when called, will remember a copy of its arguments and notify the owner |
633 | callback. |
1053 | coro of the callback. |
634 | |
1054 | |
635 | See the next function. |
1055 | See the next function. |
636 | |
1056 | |
637 | =item @args = Coro::rouse_wait [$cb] |
1057 | =item @args = rouse_wait [$cb] |
638 | |
1058 | |
639 | Wait for the specified rouse callback (or the last one tht was created in |
1059 | Wait for the specified rouse callback (or the last one that was created in |
640 | this coroutine). |
1060 | this coro). |
641 | |
1061 | |
642 | As soon as the callback is invoked (or when the calback was invoked before |
1062 | As soon as the callback is invoked (or when the callback was invoked |
643 | C<rouse_wait>), it will return a copy of the arguments originally passed |
1063 | before C<rouse_wait>), it will return the arguments originally passed to |
644 | to the rouse callback. |
1064 | the rouse callback. In scalar context, that means you get the I<last> |
|
|
1065 | argument, just as if C<rouse_wait> had a C<return ($a1, $a2, $a3...)> |
|
|
1066 | statement at the end. |
645 | |
1067 | |
646 | See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example. |
1068 | See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example. |
647 | |
1069 | |
648 | =back |
1070 | =back |
649 | |
1071 | |
650 | =cut |
1072 | =cut |
651 | |
1073 | |
|
|
1074 | for my $module (qw(Channel RWLock Semaphore SemaphoreSet Signal Specific)) { |
|
|
1075 | my $old = defined &{"Coro::$module\::new"} && \&{"Coro::$module\::new"}; |
|
|
1076 | |
|
|
1077 | *{"Coro::$module\::new"} = sub { |
|
|
1078 | require "Coro/$module.pm"; |
|
|
1079 | |
|
|
1080 | # some modules have their new predefined in State.xs, some don't |
|
|
1081 | *{"Coro::$module\::new"} = $old |
|
|
1082 | if $old; |
|
|
1083 | |
|
|
1084 | goto &{"Coro::$module\::new"}; |
|
|
1085 | }; |
|
|
1086 | } |
|
|
1087 | |
652 | 1; |
1088 | 1; |
653 | |
1089 | |
654 | =head1 HOW TO WAIT FOR A CALLBACK |
1090 | =head1 HOW TO WAIT FOR A CALLBACK |
655 | |
1091 | |
656 | It is very common for a coroutine to wait for some callback to be |
1092 | It is very common for a coro to wait for some callback to be |
657 | called. This occurs naturally when you use coroutines in an otherwise |
1093 | called. This occurs naturally when you use coro in an otherwise |
658 | event-based program, or when you use event-based libraries. |
1094 | event-based program, or when you use event-based libraries. |
659 | |
1095 | |
660 | These typically register a callback for some event, and call that callback |
1096 | These typically register a callback for some event, and call that callback |
661 | when the event occured. In a coroutine, however, you typically want to |
1097 | when the event occured. In a coro, however, you typically want to |
662 | just wait for the event, simplyifying things. |
1098 | just wait for the event, simplyifying things. |
663 | |
1099 | |
664 | For example C<< AnyEvent->child >> registers a callback to be called when |
1100 | For example C<< AnyEvent->child >> registers a callback to be called when |
665 | a specific child has exited: |
1101 | a specific child has exited: |
666 | |
1102 | |
667 | my $child_watcher = AnyEvent->child (pid => $pid, cb => sub { ... }); |
1103 | my $child_watcher = AnyEvent->child (pid => $pid, cb => sub { ... }); |
668 | |
1104 | |
669 | But from withina coroutine, you often just want to write this: |
1105 | But from within a coro, you often just want to write this: |
670 | |
1106 | |
671 | my $status = wait_for_child $pid; |
1107 | my $status = wait_for_child $pid; |
672 | |
1108 | |
673 | Coro offers two functions specifically designed to make this easy, |
1109 | Coro offers two functions specifically designed to make this easy, |
674 | C<Coro::rouse_cb> and C<Coro::rouse_wait>. |
1110 | C<Coro::rouse_cb> and C<Coro::rouse_wait>. |
675 | |
1111 | |
676 | The first function, C<rouse_cb>, generates and returns a callback that, |
1112 | The first function, C<rouse_cb>, generates and returns a callback that, |
677 | when invoked, will save it's arguments and notify the coroutine that |
1113 | when invoked, will save its arguments and notify the coro that |
678 | created the callback. |
1114 | created the callback. |
679 | |
1115 | |
680 | The second function, C<rouse_wait>, waits for the callback to be called |
1116 | The second function, C<rouse_wait>, waits for the callback to be called |
681 | (by calling C<schedule> to go to sleep) and returns the arguments |
1117 | (by calling C<schedule> to go to sleep) and returns the arguments |
682 | originally passed to the callback. |
1118 | originally passed to the callback. |
… | |
… | |
697 | you can roll your own, using C<schedule>: |
1133 | you can roll your own, using C<schedule>: |
698 | |
1134 | |
699 | sub wait_for_child($) { |
1135 | sub wait_for_child($) { |
700 | my ($pid) = @_; |
1136 | my ($pid) = @_; |
701 | |
1137 | |
702 | # store the current coroutine in $current, |
1138 | # store the current coro in $current, |
703 | # and provide result variables for the closure passed to ->child |
1139 | # and provide result variables for the closure passed to ->child |
704 | my $current = $Coro::current; |
1140 | my $current = $Coro::current; |
705 | my ($done, $rstatus); |
1141 | my ($done, $rstatus); |
706 | |
1142 | |
707 | # pass a closure to ->child |
1143 | # pass a closure to ->child |
… | |
… | |
723 | |
1159 | |
724 | =item fork with pthread backend |
1160 | =item fork with pthread backend |
725 | |
1161 | |
726 | When Coro is compiled using the pthread backend (which isn't recommended |
1162 | When Coro is compiled using the pthread backend (which isn't recommended |
727 | but required on many BSDs as their libcs are completely broken), then |
1163 | but required on many BSDs as their libcs are completely broken), then |
728 | coroutines will not survive a fork. There is no known workaround except to |
1164 | coro will not survive a fork. There is no known workaround except to |
729 | fix your libc and use a saner backend. |
1165 | fix your libc and use a saner backend. |
730 | |
1166 | |
731 | =item perl process emulation ("threads") |
1167 | =item perl process emulation ("threads") |
732 | |
1168 | |
733 | This module is not perl-pseudo-thread-safe. You should only ever use this |
1169 | This module is not perl-pseudo-thread-safe. You should only ever use this |
734 | module from the same thread (this requirement might be removed in the |
1170 | module from the first thread (this requirement might be removed in the |
735 | future to allow per-thread schedulers, but Coro::State does not yet allow |
1171 | future to allow per-thread schedulers, but Coro::State does not yet allow |
736 | this). I recommend disabling thread support and using processes, as having |
1172 | this). I recommend disabling thread support and using processes, as having |
737 | the windows process emulation enabled under unix roughly halves perl |
1173 | the windows process emulation enabled under unix roughly halves perl |
738 | performance, even when not used. |
1174 | performance, even when not used. |
739 | |
1175 | |
740 | =item coroutine switching not signal safe |
1176 | =item coro switching is not signal safe |
741 | |
1177 | |
742 | You must not switch to another coroutine from within a signal handler |
1178 | You must not switch to another coro from within a signal handler (only |
743 | (only relevant with %SIG - most event libraries provide safe signals). |
1179 | relevant with %SIG - most event libraries provide safe signals), I<unless> |
|
|
1180 | you are sure you are not interrupting a Coro function. |
744 | |
1181 | |
745 | That means you I<MUST NOT> call any function that might "block" the |
1182 | That means you I<MUST NOT> call any function that might "block" the |
746 | current coroutine - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or |
1183 | current coro - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or |
747 | anything that calls those. Everything else, including calling C<ready>, |
1184 | anything that calls those. Everything else, including calling C<ready>, |
748 | works. |
1185 | works. |
749 | |
1186 | |
750 | =back |
1187 | =back |
751 | |
1188 | |
752 | |
1189 | |
|
|
1190 | =head1 WINDOWS PROCESS EMULATION |
|
|
1191 | |
|
|
1192 | A great many people seem to be confused about ithreads (for example, Chip |
|
|
1193 | Salzenberg called me unintelligent, incapable, stupid and gullible, |
|
|
1194 | while in the same mail making rather confused statements about perl |
|
|
1195 | ithreads (for example, that memory or files would be shared), showing his |
|
|
1196 | lack of understanding of this area - if it is hard to understand for Chip, |
|
|
1197 | it is probably not obvious to everybody). |
|
|
1198 | |
|
|
1199 | What follows is an ultra-condensed version of my talk about threads in |
|
|
1200 | scripting languages given on the perl workshop 2009: |
|
|
1201 | |
|
|
1202 | The so-called "ithreads" were originally implemented for two reasons: |
|
|
1203 | first, to (badly) emulate unix processes on native win32 perls, and |
|
|
1204 | secondly, to replace the older, real thread model ("5.005-threads"). |
|
|
1205 | |
|
|
1206 | It does that by using threads instead of OS processes. The difference |
|
|
1207 | between processes and threads is that threads share memory (and other |
|
|
1208 | state, such as files) between threads within a single process, while |
|
|
1209 | processes do not share anything (at least not semantically). That |
|
|
1210 | means that modifications done by one thread are seen by others, while |
|
|
1211 | modifications by one process are not seen by other processes. |
|
|
1212 | |
|
|
1213 | The "ithreads" work exactly like that: when creating a new ithreads |
|
|
1214 | process, all state is copied (memory is copied physically, files and code |
|
|
1215 | is copied logically). Afterwards, it isolates all modifications. On UNIX, |
|
|
1216 | the same behaviour can be achieved by using operating system processes, |
|
|
1217 | except that UNIX typically uses hardware built into the system to do this |
|
|
1218 | efficiently, while the windows process emulation emulates this hardware in |
|
|
1219 | software (rather efficiently, but of course it is still much slower than |
|
|
1220 | dedicated hardware). |
|
|
1221 | |
|
|
1222 | As mentioned before, loading code, modifying code, modifying data |
|
|
1223 | structures and so on is only visible in the ithreads process doing the |
|
|
1224 | modification, not in other ithread processes within the same OS process. |
|
|
1225 | |
|
|
1226 | This is why "ithreads" do not implement threads for perl at all, only |
|
|
1227 | processes. What makes it so bad is that on non-windows platforms, you can |
|
|
1228 | actually take advantage of custom hardware for this purpose (as evidenced |
|
|
1229 | by the forks module, which gives you the (i-) threads API, just much |
|
|
1230 | faster). |
|
|
1231 | |
|
|
1232 | Sharing data is in the i-threads model is done by transfering data |
|
|
1233 | structures between threads using copying semantics, which is very slow - |
|
|
1234 | shared data simply does not exist. Benchmarks using i-threads which are |
|
|
1235 | communication-intensive show extremely bad behaviour with i-threads (in |
|
|
1236 | fact, so bad that Coro, which cannot take direct advantage of multiple |
|
|
1237 | CPUs, is often orders of magnitude faster because it shares data using |
|
|
1238 | real threads, refer to my talk for details). |
|
|
1239 | |
|
|
1240 | As summary, i-threads *use* threads to implement processes, while |
|
|
1241 | the compatible forks module *uses* processes to emulate, uhm, |
|
|
1242 | processes. I-threads slow down every perl program when enabled, and |
|
|
1243 | outside of windows, serve no (or little) practical purpose, but |
|
|
1244 | disadvantages every single-threaded Perl program. |
|
|
1245 | |
|
|
1246 | This is the reason that I try to avoid the name "ithreads", as it is |
|
|
1247 | misleading as it implies that it implements some kind of thread model for |
|
|
1248 | perl, and prefer the name "windows process emulation", which describes the |
|
|
1249 | actual use and behaviour of it much better. |
|
|
1250 | |
753 | =head1 SEE ALSO |
1251 | =head1 SEE ALSO |
754 | |
1252 | |
755 | Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>. |
1253 | Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>. |
756 | |
1254 | |
757 | Debugging: L<Coro::Debug>. |
1255 | Debugging: L<Coro::Debug>. |
758 | |
1256 | |
759 | Support/Utility: L<Coro::Specific>, L<Coro::Util>. |
1257 | Support/Utility: L<Coro::Specific>, L<Coro::Util>. |
760 | |
1258 | |
761 | Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, |
1259 | Locking and IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, |
762 | L<Coro::SemaphoreSet>, L<Coro::RWLock>. |
1260 | L<Coro::SemaphoreSet>, L<Coro::RWLock>. |
763 | |
1261 | |
764 | IO/Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>. |
1262 | I/O and Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>. |
765 | |
1263 | |
766 | Compatibility: L<Coro::LWP> (but see also L<AnyEvent::HTTP> for |
1264 | Compatibility with other modules: L<Coro::LWP> (but see also L<AnyEvent::HTTP> for |
767 | a better-working alternative), L<Coro::BDB>, L<Coro::Storable>, |
1265 | a better-working alternative), L<Coro::BDB>, L<Coro::Storable>, |
768 | L<Coro::Select>. |
1266 | L<Coro::Select>. |
769 | |
1267 | |
770 | XS API: L<Coro::MakeMaker>. |
1268 | XS API: L<Coro::MakeMaker>. |
771 | |
1269 | |
772 | Low level Configuration, Coroutine Environment: L<Coro::State>. |
1270 | Low level Configuration, Thread Environment, Continuations: L<Coro::State>. |
773 | |
1271 | |
774 | =head1 AUTHOR |
1272 | =head1 AUTHOR |
775 | |
1273 | |
776 | Marc Lehmann <schmorp@schmorp.de> |
1274 | Marc Lehmann <schmorp@schmorp.de> |
777 | http://home.schmorp.de/ |
1275 | http://home.schmorp.de/ |