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

Comparing Coro/Coro.pm (file contents):
Revision 1.96 by root, Mon Dec 4 03:48:16 2006 UTC vs.
Revision 1.134 by root, Sat Sep 22 14:42:56 2007 UTC

…		…
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 used in this module also
		26	guarantees 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
…		…
41		50
42	our $idle; # idle handler	51	our $idle; # idle handler
43	our $main; # main coroutine	52	our $main; # main coroutine
44	our $current; # current coroutine	53	our $current; # current coroutine
45		54
46	our $VERSION = '3.01';	55	our $VERSION = '3.7';
47		56
48	our @EXPORT = qw(async cede schedule terminate current unblock_sub);	57	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);
49	our %EXPORT_TAGS = (	58	our %EXPORT_TAGS = (
50	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)],
51	);	60	);
52	our @EXPORT_OK = @{$EXPORT_TAGS{prio}};	61	our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready));
53		62
54	{	63	{
55	my @async;	64	my @async;
56	my $init;	65	my $init;
57		66
…		…
99		108
100	The current coroutine (the last coroutine switched to). The initial value	109	The current coroutine (the last coroutine switched to). The initial value
101	is C<$main> (of course).	110	is C<$main> (of course).
102		111
103	This variable is B<strictly> I<read-only>. It is provided for performance	112	This variable is B<strictly> I<read-only>. It is provided for performance
104	reasons. If performance is not essentiel you are encouraged to use the	113	reasons. If performance is not essential you are encouraged to use the
105	C<Coro::current> function instead.	114	C<Coro::current> function instead.
106		115
107	=cut	116	=cut
		117
		118	$main->{desc} = "[main::]";
108		119
109	# maybe some other module used Coro::Specific before...	120	# maybe some other module used Coro::Specific before...
110	$main->{specific} = $current->{specific}	121	$main->{specific} = $current->{specific}
111	if $current;	122	if $current;
112		123
…		…
132	$idle = sub {	143	$idle = sub {
133	require Carp;	144	require Carp;
134	Carp::croak ("FATAL: deadlock detected");	145	Carp::croak ("FATAL: deadlock detected");
135	};	146	};
136		147
		148	sub _cancel {
		149	my ($self) = @_;
		150
		151	# free coroutine data and mark as destructed
		152	$self->_destroy
		153	or return;
		154
		155	# call all destruction callbacks
		156	$_->(@{$self->{status}})
		157	for @{(delete $self->{destroy_cb}) \|\| []};
		158	}
		159
137	# this coroutine is necessary because a coroutine	160	# this coroutine is necessary because a coroutine
138	# cannot destroy itself.	161	# cannot destroy itself.
139	my @destroy;	162	my @destroy;
		163	my $manager;
		164
140	my $manager; $manager = new Coro sub {	165	$manager = new Coro sub {
141	while () {	166	while () {
142	# by overwriting the state object with the manager we destroy it	167	(shift @destroy)->_cancel
143	# while still being able to schedule this coroutine (in case it has
144	# been readied multiple times. this is harmless since the manager
145	# can be called as many times as neccessary and will always
146	# remove itself from the runqueue
147	while (@destroy) {	168	while @destroy;
148	my $coro = pop @destroy;
149	$coro->{status} \|\|= [];
150	$_->ready for @{delete $coro->{join} \|\| []};
151		169
152	# the next line destroys the coro state, but keeps the
153	# coroutine itself intact (we basically make it a zombie
154	# coroutine that always runs the manager thread, so it's possible
155	# to transfer() to this coroutine).
156	$coro->_clone_state_from ($manager);
157	}
158	&schedule;	170	&schedule;
159	}	171	}
160	};	172	};
		173	$manager->desc ("[coro manager]");
		174	$manager->prio (PRIO_MAX);
161		175
162	# static methods. not really.	176	# static methods. not really.
163		177
164	=back	178	=back
165		179
…		…
173		187
174	Create a new asynchronous coroutine and return it's coroutine object	188	Create a new asynchronous coroutine and return it's coroutine object
175	(usually unused). When the sub returns the new coroutine is automatically	189	(usually unused). When the sub returns the new coroutine is automatically
176	terminated.	190	terminated.
177		191
178	Calling C<exit> in a coroutine will not work correctly, so do not do that.	192	Calling C<exit> in a coroutine will do the same as calling exit outside
179		193	the coroutine. Likewise, when the coroutine dies, the program will exit,
180	When the coroutine dies, the program will exit, just as in the main	194	just as it would in the main program.
181	program.
182		195
183	# create a new coroutine that just prints its arguments	196	# create a new coroutine that just prints its arguments
184	async {	197	async {
185	print "@_\n";	198	print "@_\n";
186	} 1,2,3,4;	199	} 1,2,3,4;
187		200
188	=cut	201	=cut
189		202
190	sub async(&@) {	203	sub async(&@) {
191	my $pid = new Coro @_;	204	my $coro = new Coro @_;
192	$pid->ready;	205	$coro->ready;
193	$pid	206	$coro
		207	}
		208
		209	=item async_pool { ... } [@args...]
		210
		211	Similar to C<async>, but uses a coroutine pool, so you should not call
		212	terminate or join (although you are allowed to), and you get a coroutine
		213	that might have executed other code already (which can be good or bad :).
		214
		215	Also, the block is executed in an C<eval> context and a warning will be
		216	issued in case of an exception instead of terminating the program, as
		217	C<async> does. As the coroutine is being reused, stuff like C<on_destroy>
		218	will not work in the expected way, unless you call terminate or cancel,
		219	which somehow defeats the purpose of pooling.
		220
		221	The priority will be reset to C<0> after each job, otherwise the coroutine
		222	will be re-used "as-is".
		223
		224	The pool size is limited to 8 idle coroutines (this can be adjusted by
		225	changing $Coro::POOL_SIZE), and there can be as many non-idle coros as
		226	required.
		227
		228	If you are concerned about pooled coroutines growing a lot because a
		229	single C<async_pool> used a lot of stackspace you can e.g. C<async_pool
		230	{ terminate }> once per second or so to slowly replenish the pool. In
		231	addition to that, when the stacks used by a handler grows larger than 16kb
		232	(adjustable with $Coro::POOL_RSS) it will also exit.
		233
		234	=cut
		235
		236	our $POOL_SIZE = 8;
		237	our $POOL_RSS = 16 * 1024;
		238	our @async_pool;
		239
		240	sub pool_handler {
		241	my $cb;
		242
		243	while () {
		244	eval {
		245	while () {
		246	$cb = &_pool_1
		247	or return;
		248
		249	&$cb;
		250
		251	return if &_pool_2;
		252
		253	undef $cb;
		254	schedule;
		255	}
		256	};
		257
		258	warn $@ if $@;
		259	}
		260	}
		261
		262	sub async_pool(&@) {
		263	# this is also inlined into the unlock_scheduler
		264	my $coro = (pop @async_pool) \|\| new Coro \&pool_handler;;
		265
		266	$coro->{_invoke} = [@_];
		267	$coro->ready;
		268
		269	$coro
194	}	270	}
195		271
196	=item schedule	272	=item schedule
197		273
198	Calls the scheduler. Please note that the current coroutine will not be put	274	Calls the scheduler. Please note that the current coroutine will not be put
…		…
211	# wake up sleeping coroutine	287	# wake up sleeping coroutine
212	$current->ready;	288	$current->ready;
213	undef $current;	289	undef $current;
214	};	290	};
215		291
216	# call schedule until event occured.	292	# call schedule until event occurred.
217	# in case we are woken up for other reasons	293	# in case we are woken up for other reasons
218	# (current still defined), loop.	294	# (current still defined), loop.
219	Coro::schedule while $current;	295	Coro::schedule while $current;
220	}	296	}
221		297
222	=item cede	298	=item cede
223		299
224	"Cede" to other coroutines. This function puts the current coroutine into the	300	"Cede" to other coroutines. This function puts the current coroutine into the
225	ready queue and calls C<schedule>, which has the effect of giving up the	301	ready queue and calls C<schedule>, which has the effect of giving up the
226	current "timeslice" to other coroutines of the same or higher priority.	302	current "timeslice" to other coroutines of the same or higher priority.
		303
		304	Returns true if at least one coroutine switch has happened.
		305
		306	=item Coro::cede_notself
		307
		308	Works like cede, but is not exported by default and will cede to any
		309	coroutine, regardless of priority, once.
		310
		311	Returns true if at least one coroutine switch has happened.
227		312
228	=item terminate [arg...]	313	=item terminate [arg...]
229		314
230	Terminates the current coroutine with the given status values (see L<cancel>).	315	Terminates the current coroutine with the given status values (see L<cancel>).
231		316
…		…
250	Create a new coroutine and return it. When the sub returns the coroutine	335	Create a new coroutine and return it. When the sub returns the coroutine
251	automatically terminates as if C<terminate> with the returned values were	336	automatically terminates as if C<terminate> with the returned values were
252	called. To make the coroutine run you must first put it into the ready queue	337	called. To make the coroutine run you must first put it into the ready queue
253	by calling the ready method.	338	by calling the ready method.
254		339
255	Calling C<exit> in a coroutine will not work correctly, so do not do that.	340	See C<async> for additional discussion.
256		341
257	=cut	342	=cut
258		343
259	sub _run_coro {	344	sub _run_coro {
260	terminate &{+shift};	345	terminate &{+shift};
…		…
277	Return wether the coroutine is currently the ready queue or not,	362	Return wether the coroutine is currently the ready queue or not,
278		363
279	=item $coroutine->cancel (arg...)	364	=item $coroutine->cancel (arg...)
280		365
281	Terminates the given coroutine and makes it return the given arguments as	366	Terminates the given coroutine and makes it return the given arguments as
282	status (default: the empty list).	367	status (default: the empty list). Never returns if the coroutine is the
		368	current coroutine.
283		369
284	=cut	370	=cut
285		371
286	sub cancel {	372	sub cancel {
287	my $self = shift;	373	my $self = shift;
288	$self->{status} = [@_];	374	$self->{status} = [@_];
		375
		376	if ($current == $self) {
289	push @destroy, $self;	377	push @destroy, $self;
290	$manager->ready;	378	$manager->ready;
291	&schedule if $current == $self;	379	&schedule while 1;
		380	} else {
		381	$self->_cancel;
		382	}
292	}	383	}
293		384
294	=item $coroutine->join	385	=item $coroutine->join
295		386
296	Wait until the coroutine terminates and return any values given to the	387	Wait until the coroutine terminates and return any values given to the
…		…
299		390
300	=cut	391	=cut
301		392
302	sub join {	393	sub join {
303	my $self = shift;	394	my $self = shift;
		395
304	unless ($self->{status}) {	396	unless ($self->{status}) {
305	push @{$self->{join}}, $current;	397	my $current = $current;
306	&schedule;	398
		399	push @{$self->{destroy_cb}}, sub {
		400	$current->ready;
		401	undef $current;
		402	};
		403
		404	&schedule while $current;
307	}	405	}
		406
308	wantarray ? @{$self->{status}} : $self->{status}[0];	407	wantarray ? @{$self->{status}} : $self->{status}[0];
		408	}
		409
		410	=item $coroutine->on_destroy (\&cb)
		411
		412	Registers a callback that is called when this coroutine gets destroyed,
		413	but before it is joined. The callback gets passed the terminate arguments,
		414	if any.
		415
		416	=cut
		417
		418	sub on_destroy {
		419	my ($self, $cb) = @_;
		420
		421	push @{ $self->{destroy_cb} }, $cb;
309	}	422	}
310		423
311	=item $oldprio = $coroutine->prio ($newprio)	424	=item $oldprio = $coroutine->prio ($newprio)
312		425
313	Sets (or gets, if the argument is missing) the priority of the	426	Sets (or gets, if the argument is missing) the priority of the
…		…
348	$old;	461	$old;
349	}	462	}
350		463
351	=back	464	=back
352		465
353	=head2 UTILITY FUNCTIONS	466	=head2 GLOBAL FUNCTIONS
354		467
355	=over 4	468	=over 4
		469
		470	=item Coro::nready
		471
		472	Returns the number of coroutines that are currently in the ready state,
		473	i.e. that can be switched to. The value C<0> means that the only runnable
		474	coroutine is the currently running one, so C<cede> would have no effect,
		475	and C<schedule> would cause a deadlock unless there is an idle handler
		476	that wakes up some coroutines.
		477
		478	=item my $guard = Coro::guard { ... }
		479
		480	This creates and returns a guard object. Nothing happens until the object
		481	gets destroyed, in which case the codeblock given as argument will be
		482	executed. This is useful to free locks or other resources in case of a
		483	runtime error or when the coroutine gets canceled, as in both cases the
		484	guard block will be executed. The guard object supports only one method,
		485	C<< ->cancel >>, which will keep the codeblock from being executed.
		486
		487	Example: set some flag and clear it again when the coroutine gets canceled
		488	or the function returns:
		489
		490	sub do_something {
		491	my $guard = Coro::guard { $busy = 0 };
		492	$busy = 1;
		493
		494	# do something that requires $busy to be true
		495	}
		496
		497	=cut
		498
		499	sub guard(&) {
		500	bless \(my $cb = $_[0]), "Coro::guard"
		501	}
		502
		503	sub Coro::guard::cancel {
		504	${$_[0]} = sub { };
		505	}
		506
		507	sub Coro::guard::DESTROY {
		508	${$_[0]}->();
		509	}
		510
356		511
357	=item unblock_sub { ... }	512	=item unblock_sub { ... }
358		513
359	This utility function takes a BLOCK or code reference and "unblocks" it,	514	This utility function takes a BLOCK or code reference and "unblocks" it,
360	returning the new coderef. This means that the new coderef will return	515	returning the new coderef. This means that the new coderef will return
361	immediately without blocking, returning nothing, while the original code	516	immediately without blocking, returning nothing, while the original code
362	ref will be called (with parameters) from within its own coroutine.	517	ref will be called (with parameters) from within its own coroutine.
363		518
364	The reason this fucntion exists is that many event libraries (such as the	519	The reason this function exists is that many event libraries (such as the
365	venerable L<Event\|Event> module) are not coroutine-safe (a weaker form	520	venerable L<Event\|Event> module) are not coroutine-safe (a weaker form
366	of thread-safety). This means you must not block within event callbacks,	521	of thread-safety). This means you must not block within event callbacks,
367	otherwise you might suffer from crashes or worse.	522	otherwise you might suffer from crashes or worse.
368		523
369	This function allows your callbacks to block by executing them in another	524	This function allows your callbacks to block by executing them in another
…		…
374	In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when	529	In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when
375	creating event callbacks that want to block.	530	creating event callbacks that want to block.
376		531
377	=cut	532	=cut
378		533
379	our @unblock_pool;
380	our @unblock_queue;	534	our @unblock_queue;
381	our $UNBLOCK_POOL_SIZE = 2;
382		535
383	sub unblock_handler_ {	536	# we create a special coro because we want to cede,
384	while () {	537	# to reduce pressure on the coro pool (because most callbacks
385	my ($cb, @arg) = @{ delete $Coro::current->{arg} };	538	# return immediately and can be reused) and because we cannot cede
386	$cb->(@arg);	539	# inside an event callback.
387
388	last if @unblock_pool >= $UNBLOCK_POOL_SIZE;
389	push @unblock_pool, $Coro::current;
390	schedule;
391	}
392	}
393
394	our $unblock_scheduler = async {	540	our $unblock_scheduler = new Coro sub {
395	while () {	541	while () {
396	while (my $cb = pop @unblock_queue) {	542	while (my $cb = pop @unblock_queue) {
397	my $handler = (pop @unblock_pool or new Coro \&unblock_handler_);	543	# this is an inlined copy of async_pool
398	$handler->{arg} = $cb;	544	my $coro = (pop @async_pool) \|\| new Coro \&pool_handler;
		545
		546	$coro->{_invoke} = $cb;
399	$handler->ready;	547	$coro->ready;
400	cede;	548	cede; # for short-lived callbacks, this reduces pressure on the coro pool
401	}	549	}
402		550	schedule; # sleep well
403	schedule;
404	}	551	}
405	};	552	};
		553	$unblock_scheduler->desc ("[unblock_sub scheduler]");
406		554
407	sub unblock_sub(&) {	555	sub unblock_sub(&) {
408	my $cb = shift;	556	my $cb = shift;
409		557
410	sub {	558	sub {
411	push @unblock_queue, [$cb, @_];	559	unshift @unblock_queue, [$cb, @_];
412	$unblock_scheduler->ready;	560	$unblock_scheduler->ready;
413	}	561	}
414	}	562	}
415		563
416	=back	564	=back
…		…
423		571
424	- you must make very sure that no coro is still active on global	572	- you must make very sure that no coro is still active on global
425	destruction. very bad things might happen otherwise (usually segfaults).	573	destruction. very bad things might happen otherwise (usually segfaults).
426		574
427	- this module is not thread-safe. You should only ever use this module	575	- this module is not thread-safe. You should only ever use this module
428	from the same thread (this requirement might be losened in the future	576	from the same thread (this requirement might be loosened in the future
429	to allow per-thread schedulers, but Coro::State does not yet allow	577	to allow per-thread schedulers, but Coro::State does not yet allow
430	this).	578	this).
431		579
432	=head1 SEE ALSO	580	=head1 SEE ALSO
433		581

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.96 by root, Mon Dec 4 03:48:16 2006 UTC vs. Revision 1.134 by root, Sat Sep 22 14:42:56 2007 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.96 by root, Mon Dec 4 03:48:16 2006 UTC vs.
Revision 1.134 by root, Sat Sep 22 14:42:56 2007 UTC