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

Comparing Coro/Coro.pm (file contents):
Revision 1.115 by root, Wed Feb 28 11:43:03 2007 UTC vs.
Revision 1.152 by root, Sun Oct 7 13:53:37 2007 UTC

…		…
6		6
7	use Coro;	7	use Coro;
8		8
9	async {	9	async {
10	# some asynchronous thread of execution	10	# some asynchronous thread of execution
		11	print "2\n";
		12	cede; # yield back to main
		13	print "4\n";
11	};	14	};
		15	print "1\n";
		16	cede; # yield to coroutine
		17	print "3\n";
		18	cede; # and again
12		19
13	# alternatively create an async coroutine like this:	20	# use locking
		21	my $lock = new Coro::Semaphore;
		22	my $locked;
14		23
15	sub some_func : Coro {	24	$lock->down;
16	# some more async code	25	$locked = 1;
17	}	26	$lock->up;
18
19	cede;
20		27
21	=head1 DESCRIPTION	28	=head1 DESCRIPTION
22		29
23	This module collection manages coroutines. Coroutines are similar	30	This module collection manages coroutines. Coroutines are similar
24	to threads but don't run in parallel at the same time even on SMP	31	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	32	machines. The specific flavor of coroutine used in this module also
26	guarentees you that it will not switch between coroutines unless	33	guarantees you that it will not switch between coroutines unless
27	necessary, at easily-identified points in your program, so locking and	34	necessary, at easily-identified points in your program, so locking and
28	parallel access are rarely an issue, making coroutine programming much	35	parallel access are rarely an issue, making coroutine programming much
29	safer than threads programming.	36	safer than threads programming.
30		37
31	(Perl, however, does not natively support real threads but instead does a	38	(Perl, however, does not natively support real threads but instead does a
…		…
33	is a performance win on Windows machines, and a loss everywhere else).	40	is a performance win on Windows machines, and a loss everywhere else).
34		41
35	In this module, coroutines are defined as "callchain + lexical variables +	42	In this module, coroutines are defined as "callchain + lexical variables +
36	@_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own callchain,	43	@_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own callchain,
37	its own set of lexicals and its own set of perls most important global	44	its own set of lexicals and its own set of perls most important global
38	variables.	45	variables (see L<Coro::State> for more configuration).
39		46
40	=cut	47	=cut
41		48
42	package Coro;	49	package Coro;
43		50
…		…
50		57
51	our $idle; # idle handler	58	our $idle; # idle handler
52	our $main; # main coroutine	59	our $main; # main coroutine
53	our $current; # current coroutine	60	our $current; # current coroutine
54		61
55	our $VERSION = '3.501';	62	our $VERSION = '4.1';
56		63
57	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);	64	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);
58	our %EXPORT_TAGS = (	65	our %EXPORT_TAGS = (
59	prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],	66	prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
60	);	67	);
…		…
108		115
109	The current coroutine (the last coroutine switched to). The initial value	116	The current coroutine (the last coroutine switched to). The initial value
110	is C<$main> (of course).	117	is C<$main> (of course).
111		118
112	This variable is B<strictly> I<read-only>. It is provided for performance	119	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	120	reasons. If performance is not essential you are encouraged to use the
114	C<Coro::current> function instead.	121	C<Coro::current> function instead.
115		122
116	=cut	123	=cut
117		124
		125	$main->{desc} = "[main::]";
		126
118	# maybe some other module used Coro::Specific before...	127	# maybe some other module used Coro::Specific before...
119	$main->{specific} = $current->{specific}	128	$main->{_specific} = $current->{_specific}
120	if $current;	129	if $current;
121		130
122	_set_current $main;	131	_set_current $main;
123		132
124	sub current() { $current }	133	sub current() { $current }
…		…
132	This hook is overwritten by modules such as C<Coro::Timer> and	141	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	142	C<Coro::Event> to wait on an external event that hopefully wake up a
134	coroutine so the scheduler can run it.	143	coroutine so the scheduler can run it.
135		144
136	Please note that if your callback recursively invokes perl (e.g. for event	145	Please note that if your callback recursively invokes perl (e.g. for event
137	handlers), then it must be prepared to be called recursively.	146	handlers), then it must be prepared to be called recursively itself.
138		147
139	=cut	148	=cut
140		149
141	$idle = sub {	150	$idle = sub {
142	require Carp;	151	require Carp;
…		…
149	# free coroutine data and mark as destructed	158	# free coroutine data and mark as destructed
150	$self->_destroy	159	$self->_destroy
151	or return;	160	or return;
152		161
153	# call all destruction callbacks	162	# call all destruction callbacks
154	$_->(@{$self->{status}})	163	$_->(@{$self->{_status}})
155	for @{(delete $self->{destroy_cb}) \|\| []};	164	for @{(delete $self->{_on_destroy}) \|\| []};
156	}	165	}
157		166
158	# this coroutine is necessary because a coroutine	167	# this coroutine is necessary because a coroutine
159	# cannot destroy itself.	168	# cannot destroy itself.
160	my @destroy;	169	my @destroy;
…		…
166	while @destroy;	175	while @destroy;
167		176
168	&schedule;	177	&schedule;
169	}	178	}
170	};	179	};
171		180	$manager->desc ("[coro manager]");
172	$manager->prio (PRIO_MAX);	181	$manager->prio (PRIO_MAX);
173		182
174	# static methods. not really.	183	# static methods. not really.
175		184
176	=back	185	=back
…		…
185		194
186	Create a new asynchronous coroutine and return it's coroutine object	195	Create a new asynchronous coroutine and return it's coroutine object
187	(usually unused). When the sub returns the new coroutine is automatically	196	(usually unused). When the sub returns the new coroutine is automatically
188	terminated.	197	terminated.
189		198
190	Calling C<exit> in a coroutine will not work correctly, so do not do that.	199	See the C<Coro::State::new> constructor for info about the coroutine
		200	environment in which coroutines run.
191		201
192	When the coroutine dies, the program will exit, just as in the main	202	Calling C<exit> in a coroutine will do the same as calling exit outside
193	program.	203	the coroutine. Likewise, when the coroutine dies, the program will exit,
		204	just as it would in the main program.
194		205
195	# create a new coroutine that just prints its arguments	206	# create a new coroutine that just prints its arguments
196	async {	207	async {
197	print "@_\n";	208	print "@_\n";
198	} 1,2,3,4;	209	} 1,2,3,4;
…		…
215	issued in case of an exception instead of terminating the program, as	226	issued in case of an exception instead of terminating the program, as
216	C<async> does. As the coroutine is being reused, stuff like C<on_destroy>	227	C<async> does. As the coroutine is being reused, stuff like C<on_destroy>
217	will not work in the expected way, unless you call terminate or cancel,	228	will not work in the expected way, unless you call terminate or cancel,
218	which somehow defeats the purpose of pooling.	229	which somehow defeats the purpose of pooling.
219		230
220	The priority will be reset to C<0> after each job, otherwise the coroutine	231	The priority will be reset to C<0> after each job, tracing will be
221	will be re-used "as-is".	232	disabled, the description will be reset and the default output filehandle
		233	gets restored, so you can change alkl these. Otherwise the coroutine will
		234	be re-used "as-is": most notably if you change other per-coroutine global
		235	stuff such as C<$/> you need to revert that change, which is most simply
		236	done by using local as in C< local $/ >.
222		237
223	The pool size is limited to 8 idle coroutines (this can be adjusted by	238	The pool size is limited to 8 idle coroutines (this can be adjusted by
224	changing $Coro::POOL_SIZE), and there can be as many non-idle coros as	239	changing $Coro::POOL_SIZE), and there can be as many non-idle coros as
225	required.	240	required.
226		241
227	If you are concerned about pooled coroutines growing a lot because a	242	If you are concerned about pooled coroutines growing a lot because a
228	single C<async_pool> used a lot of stackspace you can e.g. C<async_pool {	243	single C<async_pool> used a lot of stackspace you can e.g. C<async_pool
229	terminate }> once per second or so to slowly replenish the pool.	244	{ terminate }> once per second or so to slowly replenish the pool. In
		245	addition to that, when the stacks used by a handler grows larger than 16kb
		246	(adjustable with $Coro::POOL_RSS) it will also exit.
230		247
231	=cut	248	=cut
232		249
233	our $POOL_SIZE = 8;	250	our $POOL_SIZE = 8;
		251	our $POOL_RSS = 16 * 1024;
234	our @pool;	252	our @async_pool;
235		253
236	sub pool_handler {	254	sub pool_handler {
		255	my $cb;
		256
237	while () {	257	while () {
238	eval {	258	eval {
239	my ($cb, @arg) = @{ delete $current->{_invoke} or return };	259	while () {
240	$cb->(@arg);	260	_pool_1 $cb;
		261	&$cb;
		262	_pool_2 $cb;
		263	&schedule;
		264	}
241	};	265	};
		266
		267	last if $@ eq "\3async_pool terminate\2\n";
242	warn $@ if $@;	268	warn $@ if $@;
243
244	last if @pool >= $POOL_SIZE;
245	push @pool, $current;
246
247	$current->prio (0);
248	schedule;
249	}	269	}
250	}	270	}
251		271
252	sub async_pool(&@) {	272	sub async_pool(&@) {
253	# this is also inlined into the unlock_scheduler	273	# this is also inlined into the unlock_scheduler
254	my $coro = (pop @pool or new Coro \&pool_handler);	274	my $coro = (pop @async_pool) \|\| new Coro \&pool_handler;
255		275
256	$coro->{_invoke} = [@_];	276	$coro->{_invoke} = [@_];
257	$coro->ready;	277	$coro->ready;
258		278
259	$coro	279	$coro
…		…
277	# wake up sleeping coroutine	297	# wake up sleeping coroutine
278	$current->ready;	298	$current->ready;
279	undef $current;	299	undef $current;
280	};	300	};
281		301
282	# call schedule until event occured.	302	# call schedule until event occurred.
283	# in case we are woken up for other reasons	303	# in case we are woken up for other reasons
284	# (current still defined), loop.	304	# (current still defined), loop.
285	Coro::schedule while $current;	305	Coro::schedule while $current;
286	}	306	}
287		307
…		…
302		322
303	=item terminate [arg...]	323	=item terminate [arg...]
304		324
305	Terminates the current coroutine with the given status values (see L<cancel>).	325	Terminates the current coroutine with the given status values (see L<cancel>).
306		326
		327	=item killall
		328
		329	Kills/terminates/cancels all coroutines except the currently running
		330	one. This is useful after a fork, either in the child or the parent, as
		331	usually only one of them should inherit the running coroutines.
		332
307	=cut	333	=cut
308		334
309	sub terminate {	335	sub terminate {
310	$current->cancel (@_);	336	$current->cancel (@_);
		337	}
		338
		339	sub killall {
		340	for (Coro::State::list) {
		341	$_->cancel
		342	if $_ != $current && UNIVERSAL::isa $_, "Coro";
		343	}
311	}	344	}
312		345
313	=back	346	=back
314		347
315	# dynamic methods	348	# dynamic methods
…		…
325	Create a new coroutine and return it. When the sub returns the coroutine	358	Create a new coroutine and return it. When the sub returns the coroutine
326	automatically terminates as if C<terminate> with the returned values were	359	automatically terminates as if C<terminate> with the returned values were
327	called. To make the coroutine run you must first put it into the ready queue	360	called. To make the coroutine run you must first put it into the ready queue
328	by calling the ready method.	361	by calling the ready method.
329		362
330	Calling C<exit> in a coroutine will not work correctly, so do not do that.	363	See C<async> and C<Coro::State::new> for additional info about the
		364	coroutine environment.
331		365
332	=cut	366	=cut
333		367
334	sub _run_coro {	368	sub _run_coro {
335	terminate &{+shift};	369	terminate &{+shift};
…		…
359		393
360	=cut	394	=cut
361		395
362	sub cancel {	396	sub cancel {
363	my $self = shift;	397	my $self = shift;
364	$self->{status} = [@_];	398	$self->{_status} = [@_];
365		399
366	if ($current == $self) {	400	if ($current == $self) {
367	push @destroy, $self;	401	push @destroy, $self;
368	$manager->ready;	402	$manager->ready;
369	&schedule while 1;	403	&schedule while 1;
…		…
373	}	407	}
374		408
375	=item $coroutine->join	409	=item $coroutine->join
376		410
377	Wait until the coroutine terminates and return any values given to the	411	Wait until the coroutine terminates and return any values given to the
378	C<terminate> or C<cancel> functions. C<join> can be called multiple times	412	C<terminate> or C<cancel> functions. C<join> can be called concurrently
379	from multiple coroutine.	413	from multiple coroutines.
380		414
381	=cut	415	=cut
382		416
383	sub join {	417	sub join {
384	my $self = shift;	418	my $self = shift;
385		419
386	unless ($self->{status}) {	420	unless ($self->{_status}) {
387	my $current = $current;	421	my $current = $current;
388		422
389	push @{$self->{destroy_cb}}, sub {	423	push @{$self->{_on_destroy}}, sub {
390	$current->ready;	424	$current->ready;
391	undef $current;	425	undef $current;
392	};	426	};
393		427
394	&schedule while $current;	428	&schedule while $current;
395	}	429	}
396		430
397	wantarray ? @{$self->{status}} : $self->{status}[0];	431	wantarray ? @{$self->{_status}} : $self->{_status}[0];
398	}	432	}
399		433
400	=item $coroutine->on_destroy (\&cb)	434	=item $coroutine->on_destroy (\&cb)
401		435
402	Registers a callback that is called when this coroutine gets destroyed,	436	Registers a callback that is called when this coroutine gets destroyed,
…		…
406	=cut	440	=cut
407		441
408	sub on_destroy {	442	sub on_destroy {
409	my ($self, $cb) = @_;	443	my ($self, $cb) = @_;
410		444
411	push @{ $self->{destroy_cb} }, $cb;	445	push @{ $self->{_on_destroy} }, $cb;
412	}	446	}
413		447
414	=item $oldprio = $coroutine->prio ($newprio)	448	=item $oldprio = $coroutine->prio ($newprio)
415		449
416	Sets (or gets, if the argument is missing) the priority of the	450	Sets (or gets, if the argument is missing) the priority of the
…		…
441	=item $olddesc = $coroutine->desc ($newdesc)	475	=item $olddesc = $coroutine->desc ($newdesc)
442		476
443	Sets (or gets in case the argument is missing) the description for this	477	Sets (or gets in case the argument is missing) the description for this
444	coroutine. This is just a free-form string you can associate with a coroutine.	478	coroutine. This is just a free-form string you can associate with a coroutine.
445		479
		480	This method simply sets the C<< $coroutine->{desc} >> member to the given string. You
		481	can modify this member directly if you wish.
		482
		483	=item $coroutine->throw ([$scalar])
		484
		485	If C<$throw> is specified and defined, it will be thrown as an exception
		486	inside the coroutine at the next convinient point in time (usually after
		487	it gains control at the next schedule/transfer/cede). Otherwise clears the
		488	exception object.
		489
		490	The exception object will be thrown "as is" with the specified scalar in
		491	C<$@>, i.e. if it is a string, no line number or newline will be appended
		492	(unlike with C<die>).
		493
		494	This can be used as a softer means than C<cancel> to ask a coroutine to
		495	end itself, although there is no guarentee that the exception will lead to
		496	termination, and if the exception isn't caught it might well end the whole
		497	program.
		498
446	=cut	499	=cut
447		500
448	sub desc {	501	sub desc {
449	my $old = $_[0]{desc};	502	my $old = $_[0]{desc};
450	$_[0]{desc} = $_[1] if @_ > 1;	503	$_[0]{desc} = $_[1] if @_ > 1;
…		…
458	=over 4	511	=over 4
459		512
460	=item Coro::nready	513	=item Coro::nready
461		514
462	Returns the number of coroutines that are currently in the ready state,	515	Returns the number of coroutines that are currently in the ready state,
463	i.e. that can be swicthed to. The value C<0> means that the only runnable	516	i.e. that can be switched to. The value C<0> means that the only runnable
464	coroutine is the currently running one, so C<cede> would have no effect,	517	coroutine is the currently running one, so C<cede> would have no effect,
465	and C<schedule> would cause a deadlock unless there is an idle handler	518	and C<schedule> would cause a deadlock unless there is an idle handler
466	that wakes up some coroutines.	519	that wakes up some coroutines.
467		520
468	=item my $guard = Coro::guard { ... }	521	=item my $guard = Coro::guard { ... }
469		522
470	This creates and returns a guard object. Nothing happens until the objetc	523	This creates and returns a guard object. Nothing happens until the object
471	gets destroyed, in which case the codeblock given as argument will be	524	gets destroyed, in which case the codeblock given as argument will be
472	executed. This is useful to free locks or other resources in case of a	525	executed. This is useful to free locks or other resources in case of a
473	runtime error or when the coroutine gets canceled, as in both cases the	526	runtime error or when the coroutine gets canceled, as in both cases the
474	guard block will be executed. The guard object supports only one method,	527	guard block will be executed. The guard object supports only one method,
475	C<< ->cancel >>, which will keep the codeblock from being executed.	528	C<< ->cancel >>, which will keep the codeblock from being executed.
…		…
504	This utility function takes a BLOCK or code reference and "unblocks" it,	557	This utility function takes a BLOCK or code reference and "unblocks" it,
505	returning the new coderef. This means that the new coderef will return	558	returning the new coderef. This means that the new coderef will return
506	immediately without blocking, returning nothing, while the original code	559	immediately without blocking, returning nothing, while the original code
507	ref will be called (with parameters) from within its own coroutine.	560	ref will be called (with parameters) from within its own coroutine.
508		561
509	The reason this fucntion exists is that many event libraries (such as the	562	The reason this function exists is that many event libraries (such as the
510	venerable L<Event\|Event> module) are not coroutine-safe (a weaker form	563	venerable L<Event\|Event> module) are not coroutine-safe (a weaker form
511	of thread-safety). This means you must not block within event callbacks,	564	of thread-safety). This means you must not block within event callbacks,
512	otherwise you might suffer from crashes or worse.	565	otherwise you might suffer from crashes or worse.
513		566
514	This function allows your callbacks to block by executing them in another	567	This function allows your callbacks to block by executing them in another
…		…
525		578
526	# we create a special coro because we want to cede,	579	# we create a special coro because we want to cede,
527	# to reduce pressure on the coro pool (because most callbacks	580	# to reduce pressure on the coro pool (because most callbacks
528	# return immediately and can be reused) and because we cannot cede	581	# return immediately and can be reused) and because we cannot cede
529	# inside an event callback.	582	# inside an event callback.
530	our $unblock_scheduler = async {	583	our $unblock_scheduler = new Coro sub {
531	while () {	584	while () {
532	while (my $cb = pop @unblock_queue) {	585	while (my $cb = pop @unblock_queue) {
533	# this is an inlined copy of async_pool	586	# this is an inlined copy of async_pool
534	my $coro = (pop @pool or new Coro \&pool_handler);	587	my $coro = (pop @async_pool) \|\| new Coro \&pool_handler;
535		588
536	$coro->{_invoke} = $cb;	589	$coro->{_invoke} = $cb;
537	$coro->ready;	590	$coro->ready;
538	cede; # for short-lived callbacks, this reduces pressure on the coro pool	591	cede; # for short-lived callbacks, this reduces pressure on the coro pool
539	}	592	}
540	schedule; # sleep well	593	schedule; # sleep well
541	}	594	}
542	};	595	};
		596	$unblock_scheduler->desc ("[unblock_sub scheduler]");
543		597
544	sub unblock_sub(&) {	598	sub unblock_sub(&) {
545	my $cb = shift;	599	my $cb = shift;
546		600
547	sub {	601	sub {
…		…
560		614
561	- you must make very sure that no coro is still active on global	615	- you must make very sure that no coro is still active on global
562	destruction. very bad things might happen otherwise (usually segfaults).	616	destruction. very bad things might happen otherwise (usually segfaults).
563		617
564	- this module is not thread-safe. You should only ever use this module	618	- this module is not thread-safe. You should only ever use this module
565	from the same thread (this requirement might be losened in the future	619	from the same thread (this requirement might be loosened in the future
566	to allow per-thread schedulers, but Coro::State does not yet allow	620	to allow per-thread schedulers, but Coro::State does not yet allow
567	this).	621	this).
568		622
569	=head1 SEE ALSO	623	=head1 SEE ALSO
570		624
		625	Lower level Configuration, Coroutine Environment: L<Coro::State>.
		626
		627	Debugging: L<Coro::Debug>.
		628
571	Support/Utility: L<Coro::Cont>, L<Coro::Specific>, L<Coro::State>, L<Coro::Util>.	629	Support/Utility: L<Coro::Specific>, L<Coro::Util>.
572		630
573	Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>.	631	Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>.
574		632
575	Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::Select>.	633	Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>.
576		634
		635	Compatibility: L<Coro::LWP>, L<Coro::Storable>, L<Coro::Select>.
		636
577	Embedding: L<Coro:MakeMaker>	637	Embedding: L<Coro:MakeMaker>.
578		638
579	=head1 AUTHOR	639	=head1 AUTHOR
580		640
581	Marc Lehmann <schmorp@schmorp.de>	641	Marc Lehmann <schmorp@schmorp.de>
582	http://home.schmorp.de/	642	http://home.schmorp.de/

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.115 by root, Wed Feb 28 11:43:03 2007 UTC vs. Revision 1.152 by root, Sun Oct 7 13:53:37 2007 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.115 by root, Wed Feb 28 11:43:03 2007 UTC vs.
Revision 1.152 by root, Sun Oct 7 13:53:37 2007 UTC