[ViewVC] Diff of: cvs/Coro/Coro.pm

Comparing Coro/Coro.pm (file contents):
Revision 1.42 by root, Tue Nov 6 20:37:20 2001 UTC vs.
Revision 1.100 by root, Tue Dec 12 13:56:45 2006 UTC

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

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing Coro/Coro.pm (file contents): Revision 1.42 by root, Tue Nov 6 20:37:20 2001 UTC vs. Revision 1.100 by root, Tue Dec 12 13:56:45 2006 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.42 by root, Tue Nov 6 20:37:20 2001 UTC vs.
Revision 1.100 by root, Tue Dec 12 13:56:45 2006 UTC