1 | =head1 NAME |
1 | =head1 NAME |
2 | |
2 | |
3 | Coro - real threads in perl |
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 | |
… | |
… | |
29 | =head1 DESCRIPTION |
29 | =head1 DESCRIPTION |
30 | |
30 | |
31 | For a tutorial-style introduction, please read the L<Coro::Intro> |
31 | For a tutorial-style introduction, please read the L<Coro::Intro> |
32 | manpage. This manpage mainly contains reference information. |
32 | manpage. This manpage mainly contains reference information. |
33 | |
33 | |
34 | This module collection manages coroutines, that is, cooperative |
34 | This module collection manages continuations in general, most often |
35 | threads. Coroutines are similar to kernel threads but don't (in general) |
35 | in the form of cooperative threads (also called coroutines in the |
|
|
36 | documentation). They are similar to kernel threads but don't (in general) |
36 | run in parallel at the same time even on SMP machines. The specific flavor |
37 | run in parallel at the same time even on SMP machines. The specific flavor |
37 | of coroutine used in this module also guarantees you that it will not |
38 | of thread offered by this module also guarantees you that it will not |
38 | switch between coroutines unless necessary, at easily-identified points |
39 | switch between threads unless necessary, at easily-identified points in |
39 | in your program, so locking and parallel access are rarely an issue, |
40 | your program, so locking and parallel access are rarely an issue, making |
40 | making coroutine programming much safer and easier than using other thread |
41 | thread programming much safer and easier than using other thread models. |
41 | models. |
|
|
42 | |
42 | |
43 | Unlike the so-called "Perl threads" (which are not actually real threads |
43 | Unlike the so-called "Perl threads" (which are not actually real threads |
44 | but only the windows process emulation ported to unix), Coro provides a |
44 | but only the windows process emulation ported to unix), Coro provides a |
45 | full shared address space, which makes communication between coroutines |
45 | full shared address space, which makes communication between threads |
46 | very easy. And coroutines are fast, too: disabling the Windows process |
46 | very easy. And threads are fast, too: disabling the Windows process |
47 | emulation code in your perl and using Coro can easily result in a two to |
47 | emulation code in your perl and using Coro can easily result in a two to |
48 | four times speed increase for your programs. |
48 | four times speed increase for your programs. |
49 | |
49 | |
50 | Coro achieves that by supporting multiple running interpreters that share |
50 | Coro achieves that by supporting multiple running interpreters that share |
51 | data, which is especially useful to code pseudo-parallel processes and |
51 | data, which is especially useful to code pseudo-parallel processes and |
52 | for event-based programming, such as multiple HTTP-GET requests running |
52 | for event-based programming, such as multiple HTTP-GET requests running |
53 | concurrently. See L<Coro::AnyEvent> to learn more on how to integrate Coro |
53 | concurrently. See L<Coro::AnyEvent> to learn more on how to integrate Coro |
54 | into an event-based environment. |
54 | into an event-based environment. |
55 | |
55 | |
56 | In this module, a coroutines is defined as "callchain + lexical variables |
56 | In this module, a thread is defined as "callchain + lexical variables + |
57 | + @_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own |
57 | @_ + $_ + $@ + $/ + C stack), that is, a thread has its own callchain, |
58 | callchain, its own set of lexicals and its own set of perls most important |
58 | its own set of lexicals and its own set of perls most important global |
59 | global variables (see L<Coro::State> for more configuration and background |
59 | variables (see L<Coro::State> for more configuration and background info). |
60 | info). |
|
|
61 | |
60 | |
62 | See also the C<SEE ALSO> section at the end of this document - the Coro |
61 | See also the C<SEE ALSO> section at the end of this document - the Coro |
63 | module family is quite large. |
62 | module family is quite large. |
64 | |
63 | |
65 | =cut |
64 | =cut |
… | |
… | |
75 | |
74 | |
76 | our $idle; # idle handler |
75 | our $idle; # idle handler |
77 | our $main; # main coroutine |
76 | our $main; # main coroutine |
78 | our $current; # current coroutine |
77 | our $current; # current coroutine |
79 | |
78 | |
80 | our $VERSION = "5.0"; |
79 | our $VERSION = 5.11; |
81 | |
80 | |
82 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
81 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
83 | our %EXPORT_TAGS = ( |
82 | our %EXPORT_TAGS = ( |
84 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
83 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
85 | ); |
84 | ); |
… | |
… | |
115 | sub current() { $current } # [DEPRECATED] |
114 | sub current() { $current } # [DEPRECATED] |
116 | |
115 | |
117 | =item $Coro::idle |
116 | =item $Coro::idle |
118 | |
117 | |
119 | This variable is mainly useful to integrate Coro into event loops. It is |
118 | This variable is mainly useful to integrate Coro into event loops. It is |
120 | usually better to rely on L<Coro::AnyEvent> or LC<Coro::EV>, as this is |
119 | usually better to rely on L<Coro::AnyEvent> or L<Coro::EV>, as this is |
121 | pretty low-level functionality. |
120 | pretty low-level functionality. |
122 | |
121 | |
123 | This variable stores a callback that is called whenever the scheduler |
122 | This variable stores either a coroutine or a callback. |
|
|
123 | |
|
|
124 | If it is a callback, the it is called whenever the scheduler finds no |
124 | finds no ready coroutines to run. The default implementation prints |
125 | ready coroutines to run. The default implementation prints "FATAL: |
125 | "FATAL: deadlock detected" and exits, because the program has no other way |
126 | deadlock detected" and exits, because the program has no other way to |
126 | to continue. |
127 | continue. |
127 | |
128 | |
|
|
129 | If it is a coroutine object, then this object will be readied (without |
|
|
130 | invoking any ready hooks, however) when the scheduler finds no other ready |
|
|
131 | coroutines to run. |
|
|
132 | |
128 | This hook is overwritten by modules such as C<Coro::Timer> and |
133 | This hook is overwritten by modules such as C<Coro::EV> and |
129 | C<Coro::AnyEvent> to wait on an external event that hopefully wake up a |
134 | C<Coro::AnyEvent> to wait on an external event that hopefully wake up a |
130 | coroutine so the scheduler can run it. |
135 | coroutine so the scheduler can run it. |
131 | |
136 | |
132 | Note that the callback I<must not>, under any circumstances, block |
137 | Note that the callback I<must not>, under any circumstances, block |
133 | the current coroutine. Normally, this is achieved by having an "idle |
138 | the current coroutine. Normally, this is achieved by having an "idle |
134 | coroutine" that calls the event loop and then blocks again, and then |
139 | coroutine" that calls the event loop and then blocks again, and then |
135 | readying that coroutine in the idle handler. |
140 | readying that coroutine in the idle handler, or by simply placing the idle |
|
|
141 | coroutine in this variable. |
136 | |
142 | |
137 | See L<Coro::Event> or L<Coro::AnyEvent> for examples of using this |
143 | See L<Coro::Event> or L<Coro::AnyEvent> for examples of using this |
138 | technique. |
144 | technique. |
139 | |
145 | |
140 | Please note that if your callback recursively invokes perl (e.g. for event |
146 | Please note that if your callback recursively invokes perl (e.g. for event |
… | |
… | |
169 | |
175 | |
170 | =over 4 |
176 | =over 4 |
171 | |
177 | |
172 | =item async { ... } [@args...] |
178 | =item async { ... } [@args...] |
173 | |
179 | |
174 | Create a new coroutine and return it's coroutine object (usually |
180 | Create a new coroutine and return its coroutine object (usually |
175 | unused). The coroutine will be put into the ready queue, so |
181 | unused). The coroutine will be put into the ready queue, so |
176 | it will start running automatically on the next scheduler run. |
182 | it will start running automatically on the next scheduler run. |
177 | |
183 | |
178 | The first argument is a codeblock/closure that should be executed in the |
184 | The first argument is a codeblock/closure that should be executed in the |
179 | coroutine. When it returns argument returns the coroutine is automatically |
185 | coroutine. When it returns argument returns the coroutine is automatically |
… | |
… | |
573 | original code ref will be called (with parameters) from within another |
579 | original code ref will be called (with parameters) from within another |
574 | coroutine. |
580 | coroutine. |
575 | |
581 | |
576 | The reason this function exists is that many event libraries (such as the |
582 | The reason this function exists is that many event libraries (such as the |
577 | venerable L<Event|Event> module) are not coroutine-safe (a weaker form |
583 | venerable L<Event|Event> module) are not coroutine-safe (a weaker form |
578 | of thread-safety). This means you must not block within event callbacks, |
584 | of reentrancy). This means you must not block within event callbacks, |
579 | otherwise you might suffer from crashes or worse. The only event library |
585 | otherwise you might suffer from crashes or worse. The only event library |
580 | currently known that is safe to use without C<unblock_sub> is L<EV>. |
586 | currently known that is safe to use without C<unblock_sub> is L<EV>. |
581 | |
587 | |
582 | This function allows your callbacks to block by executing them in another |
588 | This function allows your callbacks to block by executing them in another |
583 | coroutine where it is safe to block. One example where blocking is handy |
589 | coroutine where it is safe to block. One example where blocking is handy |
… | |
… | |
629 | } |
635 | } |
630 | } |
636 | } |
631 | |
637 | |
632 | =item $cb = Coro::rouse_cb |
638 | =item $cb = Coro::rouse_cb |
633 | |
639 | |
634 | Create and return a "rouse callback". That's a code reference that, when |
640 | Create and return a "rouse callback". That's a code reference that, |
635 | called, will save its arguments and notify the owner coroutine of the |
641 | when called, will remember a copy of its arguments and notify the owner |
636 | callback. |
642 | coroutine of the callback. |
637 | |
643 | |
638 | See the next function. |
644 | See the next function. |
639 | |
645 | |
640 | =item @args = Coro::rouse_wait [$cb] |
646 | =item @args = Coro::rouse_wait [$cb] |
641 | |
647 | |
642 | Wait for the specified rouse callback (or the last one tht was created in |
648 | Wait for the specified rouse callback (or the last one that was created in |
643 | this coroutine). |
649 | this coroutine). |
644 | |
650 | |
645 | As soon as the callback is invoked (or when the calback was invoked before |
651 | As soon as the callback is invoked (or when the callback was invoked |
646 | C<rouse_wait>), it will return a copy of the arguments originally passed |
652 | before C<rouse_wait>), it will return the arguments originally passed to |
647 | to the rouse callback. |
653 | the rouse callback. |
648 | |
654 | |
649 | See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example. |
655 | See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example. |
650 | |
656 | |
651 | =back |
657 | =back |
652 | |
658 | |
… | |
… | |
675 | |
681 | |
676 | Coro offers two functions specifically designed to make this easy, |
682 | Coro offers two functions specifically designed to make this easy, |
677 | C<Coro::rouse_cb> and C<Coro::rouse_wait>. |
683 | C<Coro::rouse_cb> and C<Coro::rouse_wait>. |
678 | |
684 | |
679 | The first function, C<rouse_cb>, generates and returns a callback that, |
685 | The first function, C<rouse_cb>, generates and returns a callback that, |
680 | when invoked, will save it's arguments and notify the coroutine that |
686 | when invoked, will save its arguments and notify the coroutine that |
681 | created the callback. |
687 | created the callback. |
682 | |
688 | |
683 | The second function, C<rouse_wait>, waits for the callback to be called |
689 | The second function, C<rouse_wait>, waits for the callback to be called |
684 | (by calling C<schedule> to go to sleep) and returns the arguments |
690 | (by calling C<schedule> to go to sleep) and returns the arguments |
685 | originally passed to the callback. |
691 | originally passed to the callback. |
… | |
… | |
732 | fix your libc and use a saner backend. |
738 | fix your libc and use a saner backend. |
733 | |
739 | |
734 | =item perl process emulation ("threads") |
740 | =item perl process emulation ("threads") |
735 | |
741 | |
736 | This module is not perl-pseudo-thread-safe. You should only ever use this |
742 | This module is not perl-pseudo-thread-safe. You should only ever use this |
737 | module from the same thread (this requirement might be removed in the |
743 | module from the first thread (this requirement might be removed in the |
738 | future to allow per-thread schedulers, but Coro::State does not yet allow |
744 | future to allow per-thread schedulers, but Coro::State does not yet allow |
739 | this). I recommend disabling thread support and using processes, as having |
745 | this). I recommend disabling thread support and using processes, as having |
740 | the windows process emulation enabled under unix roughly halves perl |
746 | the windows process emulation enabled under unix roughly halves perl |
741 | performance, even when not used. |
747 | performance, even when not used. |
742 | |
748 | |
… | |
… | |
759 | |
765 | |
760 | Debugging: L<Coro::Debug>. |
766 | Debugging: L<Coro::Debug>. |
761 | |
767 | |
762 | Support/Utility: L<Coro::Specific>, L<Coro::Util>. |
768 | Support/Utility: L<Coro::Specific>, L<Coro::Util>. |
763 | |
769 | |
764 | Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, |
770 | Locking and IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, |
765 | L<Coro::SemaphoreSet>, L<Coro::RWLock>. |
771 | L<Coro::SemaphoreSet>, L<Coro::RWLock>. |
766 | |
772 | |
767 | IO/Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>. |
773 | I/O and Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>. |
768 | |
774 | |
769 | Compatibility: L<Coro::LWP> (but see also L<AnyEvent::HTTP> for |
775 | Compatibility with other modules: L<Coro::LWP> (but see also L<AnyEvent::HTTP> for |
770 | a better-working alternative), L<Coro::BDB>, L<Coro::Storable>, |
776 | a better-working alternative), L<Coro::BDB>, L<Coro::Storable>, |
771 | L<Coro::Select>. |
777 | L<Coro::Select>. |
772 | |
778 | |
773 | XS API: L<Coro::MakeMaker>. |
779 | XS API: L<Coro::MakeMaker>. |
774 | |
780 | |
775 | Low level Configuration, Coroutine Environment: L<Coro::State>. |
781 | Low level Configuration, Thread Environment, Continuations: L<Coro::State>. |
776 | |
782 | |
777 | =head1 AUTHOR |
783 | =head1 AUTHOR |
778 | |
784 | |
779 | Marc Lehmann <schmorp@schmorp.de> |
785 | Marc Lehmann <schmorp@schmorp.de> |
780 | http://home.schmorp.de/ |
786 | http://home.schmorp.de/ |