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

Comparing Coro/Coro.pm (file contents):
Revision 1.15 by root, Tue Jul 17 02:55:29 2001 UTC vs.
Revision 1.148 by root, Fri Oct 5 20:11:25 2007 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	yield;	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
26	This module is still experimental, see the BUGS section below.	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
		35	In this module, coroutines are defined as "callchain + lexical variables +
		36	@_ + $_ + $@ + $/ + 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
		38	variables.
27		39
28	=cut	40	=cut
29		41
30	package Coro;	42	package Coro;
31		43
		44	use strict;
		45	no warnings "uninitialized";
		46
32	use Coro::State;	47	use Coro::State;
33		48
34	use base Exporter;	49	use base qw(Coro::State Exporter);
35		50
36	$VERSION = 0.06;	51	our $idle; # idle handler
		52	our $main; # main coroutine
		53	our $current; # current coroutine
37		54
38	@EXPORT = qw(async yield schedule terminate);	55	our $VERSION = '4.01';
39	@EXPORT_OK = qw($current);	56
		57	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);
		58	our %EXPORT_TAGS = (
		59	prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
		60	);
		61	our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready));
40		62
41	{	63	{
42	use subs 'async';
43
44	my @async;	64	my @async;
		65	my $init;
45		66
46	# this way of handling attributes simply is NOT scalable ;()	67	# this way of handling attributes simply is NOT scalable ;()
47	sub import {	68	sub import {
		69	no strict 'refs';
		70
48	Coro->export_to_level(1, @_);	71	Coro->export_to_level (1, @_);
		72
49	my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};	73	my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};
50	*{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"} = sub {	74	*{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"} = sub {
51	my ($package, $ref) = (shift, shift);	75	my ($package, $ref) = (shift, shift);
52	my @attrs;	76	my @attrs;
53	for (@_) {	77	for (@_) {
54	if ($_ eq "Coro") {	78	if ($_ eq "Coro") {
55	push @async, $ref;	79	push @async, $ref;
		80	unless ($init++) {
		81	eval q{
		82	sub INIT {
		83	&async(pop @async) while @async;
		84	}
		85	};
		86	}
56	} else {	87	} else {
57	push @attrs, @_;	88	push @attrs, $_;
58	}	89	}
59	}	90	}
60	return $old ? $old->($package, $name, @attrs) : @attrs;	91	return $old ? $old->($package, $ref, @attrs) : @attrs;
61	};	92	};
62	}	93	}
63		94
64	sub INIT {
65	async pop @async while @async;
66	}
67	}	95	}
		96
		97	=over 4
68		98
69	=item $main	99	=item $main
70		100
71	This coroutine represents the main program.	101	This coroutine represents the main program.
72		102
73	=cut	103	=cut
74		104
75	our $main = new Coro;	105	$main = new Coro;
76		106
77	=item $current	107	=item $current (or as function: current)
78		108
79	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).
80		111
		112	This variable is B<strictly> I<read-only>. It is provided for performance
		113	reasons. If performance is not essential you are encouraged to use the
		114	C<Coro::current> function instead.
		115
81	=cut	116	=cut
		117
		118	$main->{desc} = "[main::]";
82		119
83	# maybe some other module used Coro::Specific before...	120	# maybe some other module used Coro::Specific before...
84	if ($current) {
85	$main->{specific} = $current->{specific};	121	$main->{_specific} = $current->{_specific}
86	}	122	if $current;
87		123
88	our $current = $main;	124	_set_current $main;
		125
		126	sub current() { $current }
89		127
90	=item $idle	128	=item $idle
91		129
92	The coroutine to switch to when no other coroutine is running. The default	130	A callback that is called whenever the scheduler finds no ready coroutines
93	implementation prints "FATAL: deadlock detected" and exits.	131	to run. The default implementation prints "FATAL: deadlock detected" and
		132	exits, because the program has no other way to continue.
94		133
95	=cut	134	This hook is overwritten by modules such as C<Coro::Timer> and
		135	C<Coro::Event> to wait on an external event that hopefully wake up a
		136	coroutine so the scheduler can run it.
96		137
97	# should be done using priorities :(	138	Please note that if your callback recursively invokes perl (e.g. for event
98	our $idle = new Coro sub {	139	handlers), then it must be prepared to be called recursively.
99	print STDERR "FATAL: deadlock detected\n";	140
100	exit(51);	141	=cut
		142
		143	$idle = sub {
		144	require Carp;
		145	Carp::croak ("FATAL: deadlock detected");
101	};	146	};
102		147
103	# we really need priorities...	148	sub _cancel {
104	## my @ready; #d#	149	my ($self) = @_;
105	our @ready = (); # the ready queue. hehe, rather broken ;)	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->{_on_destroy}) \|\| []};
		158	}
		159
		160	# this coroutine is necessary because a coroutine
		161	# cannot destroy itself.
		162	my @destroy;
		163	my $manager;
		164
		165	$manager = new Coro sub {
		166	while () {
		167	(shift @destroy)->_cancel
		168	while @destroy;
		169
		170	&schedule;
		171	}
		172	};
		173	$manager->desc ("[coro manager]");
		174	$manager->prio (PRIO_MAX);
106		175
107	# static methods. not really.	176	# static methods. not really.
108		177
		178	=back
		179
109	=head2 STATIC METHODS	180	=head2 STATIC METHODS
110		181
111	Static methods are actually functions that operate on the current process only.	182	Static methods are actually functions that operate on the current coroutine only.
112		183
113	=over 4	184	=over 4
114		185
115	=item async { ... } [@args...]	186	=item async { ... } [@args...]
116		187
117	Create a new asynchronous process and return it's process object	188	Create a new asynchronous coroutine and return it's coroutine object
118	(usually unused). When the sub returns the new process is automatically	189	(usually unused). When the sub returns the new coroutine is automatically
119	terminated.	190	terminated.
		191
		192	See the C<Coro::State::new> constructor for info about the coroutine
		193	environment.
		194
		195	Calling C<exit> in a coroutine will do the same as calling exit outside
		196	the coroutine. Likewise, when the coroutine dies, the program will exit,
		197	just as it would in the main program.
120		198
121	# create a new coroutine that just prints its arguments	199	# create a new coroutine that just prints its arguments
122	async {	200	async {
123	print "@_\n";	201	print "@_\n";
124	} 1,2,3,4;	202	} 1,2,3,4;
125		203
126	The coderef you submit MUST NOT be a closure that refers to variables
127	in an outer scope. This does NOT work. Pass arguments into it instead.
128
129	=cut	204	=cut
130		205
131	sub async(&@) {	206	sub async(&@) {
132	my $pid = new Coro @_;	207	my $coro = new Coro @_;
133	$pid->ready;	208	$coro->ready;
134	$pid;	209	$coro
		210	}
		211
		212	=item async_pool { ... } [@args...]
		213
		214	Similar to C<async>, but uses a coroutine pool, so you should not call
		215	terminate or join (although you are allowed to), and you get a coroutine
		216	that might have executed other code already (which can be good or bad :).
		217
		218	Also, the block is executed in an C<eval> context and a warning will be
		219	issued in case of an exception instead of terminating the program, as
		220	C<async> does. As the coroutine is being reused, stuff like C<on_destroy>
		221	will not work in the expected way, unless you call terminate or cancel,
		222	which somehow defeats the purpose of pooling.
		223
		224	The priority will be reset to C<0> after each job, tracing will be
		225	disabled, the description will be reset and the default output filehandle
		226	gets restored, so you can change alkl these. Otherwise the coroutine will
		227	be re-used "as-is": most notably if you change other per-coroutine global
		228	stuff such as C<$/> you need to revert that change, which is most simply
		229	done by using local as in C< local $/ >.
		230
		231	The pool size is limited to 8 idle coroutines (this can be adjusted by
		232	changing $Coro::POOL_SIZE), and there can be as many non-idle coros as
		233	required.
		234
		235	If you are concerned about pooled coroutines growing a lot because a
		236	single C<async_pool> used a lot of stackspace you can e.g. C<async_pool
		237	{ terminate }> once per second or so to slowly replenish the pool. In
		238	addition to that, when the stacks used by a handler grows larger than 16kb
		239	(adjustable with $Coro::POOL_RSS) it will also exit.
		240
		241	=cut
		242
		243	our $POOL_SIZE = 8;
		244	our $POOL_RSS = 16 * 1024;
		245	our @async_pool;
		246
		247	sub pool_handler {
		248	my $cb;
		249
		250	while () {
		251	eval {
		252	while () {
		253	_pool_1 $cb;
		254	&$cb;
		255	_pool_2 $cb;
		256	&schedule;
		257	}
		258	};
		259
		260	last if $@ eq "\3terminate\2\n";
		261	warn $@ if $@;
		262	}
		263	}
		264
		265	sub async_pool(&@) {
		266	# this is also inlined into the unlock_scheduler
		267	my $coro = (pop @async_pool) \|\| new Coro \&pool_handler;
		268
		269	$coro->{_invoke} = [@_];
		270	$coro->ready;
		271
		272	$coro
135	}	273	}
136		274
137	=item schedule	275	=item schedule
138		276
139	Calls the scheduler. Please note that the current process will not be put	277	Calls the scheduler. Please note that the current coroutine will not be put
140	into the ready queue, so calling this function usually means you will	278	into the ready queue, so calling this function usually means you will
141	never be called again.	279	never be called again unless something else (e.g. an event handler) calls
		280	ready.
142		281
143	=cut	282	The canonical way to wait on external events is this:
144		283
145	my $prev;	284	{
		285	# remember current coroutine
		286	my $current = $Coro::current;
146		287
147	sub schedule {	288	# register a hypothetical event handler
148	# should be done using priorities :(	289	on_event_invoke sub {
149	($prev, $current) = ($current, shift @ready \|\| $idle);	290	# wake up sleeping coroutine
150	Coro::State::transfer($prev, $current);
151	}
152
153	=item yield
154
155	Yield to other processes. This function puts the current process into the
156	ready queue and calls C<schedule>.
157
158	=cut
159
160	sub yield {
161	$current->ready;	291	$current->ready;
162	&schedule;	292	undef $current;
163	}	293	};
164		294
		295	# call schedule until event occurred.
		296	# in case we are woken up for other reasons
		297	# (current still defined), loop.
		298	Coro::schedule while $current;
		299	}
		300
		301	=item cede
		302
		303	"Cede" to other coroutines. This function puts the current coroutine into the
		304	ready queue and calls C<schedule>, which has the effect of giving up the
		305	current "timeslice" to other coroutines of the same or higher priority.
		306
		307	Returns true if at least one coroutine switch has happened.
		308
		309	=item Coro::cede_notself
		310
		311	Works like cede, but is not exported by default and will cede to any
		312	coroutine, regardless of priority, once.
		313
		314	Returns true if at least one coroutine switch has happened.
		315
165	=item terminate	316	=item terminate [arg...]
166		317
167	Terminates the current process.	318	Terminates the current coroutine with the given status values (see L<cancel>).
168		319
169	Future versions of this function will allow result arguments.	320	=item killall
		321
		322	Kills/terminates/cancels all coroutines except the currently running
		323	one. This is useful after a fork, either in the child or the parent, as
		324	usually only one of them should inherit the running coroutines.
170		325
171	=cut	326	=cut
172		327
173	sub terminate {	328	sub terminate {
174	$current->{_results} = [@_];	329	$current->cancel (@_);
175	&schedule;	330	}
		331
		332	sub killall {
		333	for (Coro::State::list) {
		334	$_->cancel
		335	if $_ != $current && UNIVERSAL::isa $_, "Coro";
		336	}
176	}	337	}
177		338
178	=back	339	=back
179		340
180	# dynamic methods	341	# dynamic methods
181		342
182	=head2 PROCESS METHODS	343	=head2 COROUTINE METHODS
183		344
184	These are the methods you can call on process objects.	345	These are the methods you can call on coroutine objects.
185		346
186	=over 4	347	=over 4
187		348
188	=item new Coro \&sub [, @args...]	349	=item new Coro \&sub [, @args...]
189		350
190	Create a new process and return it. When the sub returns the process	351	Create a new coroutine and return it. When the sub returns the coroutine
191	automatically terminates. To start the process you must first put it into	352	automatically terminates as if C<terminate> with the returned values were
		353	called. To make the coroutine run you must first put it into the ready queue
192	the ready queue by calling the ready method.	354	by calling the ready method.
193		355
194	The coderef you submit MUST NOT be a closure that refers to variables	356	See C<async> and C<Coro::State::new> for additional info about the
195	in an outer scope. This does NOT work. Pass arguments into it instead.	357	coroutine environment.
196		358
197	=cut	359	=cut
198		360
199	sub _newcoro {	361	sub _run_coro {
200	terminate &{+shift};	362	terminate &{+shift};
201	}	363	}
202		364
203	sub new {	365	sub new {
204	my $class = shift;	366	my $class = shift;
205	bless {
206	_coro_state => (new Coro::State $_[0] && \&_newcoro, @_),
207	}, $class;
208	}
209		367
210	=item $process->ready	368	$class->SUPER::new (\&_run_coro, @_)
		369	}
211		370
212	Put the current process into the ready queue.	371	=item $success = $coroutine->ready
213		372
214	=cut	373	Put the given coroutine into the ready queue (according to it's priority)
		374	and return true. If the coroutine is already in the ready queue, do nothing
		375	and return false.
215		376
216	sub ready {	377	=item $is_ready = $coroutine->is_ready
217	push @ready, $_[0];	378
		379	Return wether the coroutine is currently the ready queue or not,
		380
		381	=item $coroutine->cancel (arg...)
		382
		383	Terminates the given coroutine and makes it return the given arguments as
		384	status (default: the empty list). Never returns if the coroutine is the
		385	current coroutine.
		386
		387	=cut
		388
		389	sub cancel {
		390	my $self = shift;
		391	$self->{_status} = [@_];
		392
		393	if ($current == $self) {
		394	push @destroy, $self;
		395	$manager->ready;
		396	&schedule while 1;
		397	} else {
		398	$self->_cancel;
		399	}
		400	}
		401
		402	=item $coroutine->join
		403
		404	Wait until the coroutine terminates and return any values given to the
		405	C<terminate> or C<cancel> functions. C<join> can be called concurrently
		406	from multiple coroutines.
		407
		408	=cut
		409
		410	sub join {
		411	my $self = shift;
		412
		413	unless ($self->{_status}) {
		414	my $current = $current;
		415
		416	push @{$self->{_on_destroy}}, sub {
		417	$current->ready;
		418	undef $current;
		419	};
		420
		421	&schedule while $current;
		422	}
		423
		424	wantarray ? @{$self->{_status}} : $self->{_status}[0];
		425	}
		426
		427	=item $coroutine->on_destroy (\&cb)
		428
		429	Registers a callback that is called when this coroutine gets destroyed,
		430	but before it is joined. The callback gets passed the terminate arguments,
		431	if any.
		432
		433	=cut
		434
		435	sub on_destroy {
		436	my ($self, $cb) = @_;
		437
		438	push @{ $self->{_on_destroy} }, $cb;
		439	}
		440
		441	=item $oldprio = $coroutine->prio ($newprio)
		442
		443	Sets (or gets, if the argument is missing) the priority of the
		444	coroutine. Higher priority coroutines get run before lower priority
		445	coroutines. Priorities are small signed integers (currently -4 .. +3),
		446	that you can refer to using PRIO_xxx constants (use the import tag :prio
		447	to get then):
		448
		449	PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN
		450	3 > 1 > 0 > -1 > -3 > -4
		451
		452	# set priority to HIGH
		453	current->prio(PRIO_HIGH);
		454
		455	The idle coroutine ($Coro::idle) always has a lower priority than any
		456	existing coroutine.
		457
		458	Changing the priority of the current coroutine will take effect immediately,
		459	but changing the priority of coroutines in the ready queue (but not
		460	running) will only take effect after the next schedule (of that
		461	coroutine). This is a bug that will be fixed in some future version.
		462
		463	=item $newprio = $coroutine->nice ($change)
		464
		465	Similar to C<prio>, but subtract the given value from the priority (i.e.
		466	higher values mean lower priority, just as in unix).
		467
		468	=item $olddesc = $coroutine->desc ($newdesc)
		469
		470	Sets (or gets in case the argument is missing) the description for this
		471	coroutine. This is just a free-form string you can associate with a coroutine.
		472
		473	This method simply sets the C<< $coroutine->{desc} >> member to the given string. You
		474	can modify this member directly if you wish.
		475
		476	=cut
		477
		478	sub desc {
		479	my $old = $_[0]{desc};
		480	$_[0]{desc} = $_[1] if @_ > 1;
		481	$old;
218	}	482	}
219		483
220	=back	484	=back
221		485
		486	=head2 GLOBAL FUNCTIONS
		487
		488	=over 4
		489
		490	=item Coro::nready
		491
		492	Returns the number of coroutines that are currently in the ready state,
		493	i.e. that can be switched to. The value C<0> means that the only runnable
		494	coroutine is the currently running one, so C<cede> would have no effect,
		495	and C<schedule> would cause a deadlock unless there is an idle handler
		496	that wakes up some coroutines.
		497
		498	=item my $guard = Coro::guard { ... }
		499
		500	This creates and returns a guard object. Nothing happens until the object
		501	gets destroyed, in which case the codeblock given as argument will be
		502	executed. This is useful to free locks or other resources in case of a
		503	runtime error or when the coroutine gets canceled, as in both cases the
		504	guard block will be executed. The guard object supports only one method,
		505	C<< ->cancel >>, which will keep the codeblock from being executed.
		506
		507	Example: set some flag and clear it again when the coroutine gets canceled
		508	or the function returns:
		509
		510	sub do_something {
		511	my $guard = Coro::guard { $busy = 0 };
		512	$busy = 1;
		513
		514	# do something that requires $busy to be true
		515	}
		516
		517	=cut
		518
		519	sub guard(&) {
		520	bless \(my $cb = $_[0]), "Coro::guard"
		521	}
		522
		523	sub Coro::guard::cancel {
		524	${$_[0]} = sub { };
		525	}
		526
		527	sub Coro::guard::DESTROY {
		528	${$_[0]}->();
		529	}
		530
		531
		532	=item unblock_sub { ... }
		533
		534	This utility function takes a BLOCK or code reference and "unblocks" it,
		535	returning the new coderef. This means that the new coderef will return
		536	immediately without blocking, returning nothing, while the original code
		537	ref will be called (with parameters) from within its own coroutine.
		538
		539	The reason this function exists is that many event libraries (such as the
		540	venerable L<Event\|Event> module) are not coroutine-safe (a weaker form
		541	of thread-safety). This means you must not block within event callbacks,
		542	otherwise you might suffer from crashes or worse.
		543
		544	This function allows your callbacks to block by executing them in another
		545	coroutine where it is safe to block. One example where blocking is handy
		546	is when you use the L<Coro::AIO\|Coro::AIO> functions to save results to
		547	disk.
		548
		549	In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when
		550	creating event callbacks that want to block.
		551
		552	=cut
		553
		554	our @unblock_queue;
		555
		556	# we create a special coro because we want to cede,
		557	# to reduce pressure on the coro pool (because most callbacks
		558	# return immediately and can be reused) and because we cannot cede
		559	# inside an event callback.
		560	our $unblock_scheduler = new Coro sub {
		561	while () {
		562	while (my $cb = pop @unblock_queue) {
		563	# this is an inlined copy of async_pool
		564	my $coro = (pop @async_pool) \|\| new Coro \&pool_handler;
		565
		566	$coro->{_invoke} = $cb;
		567	$coro->ready;
		568	cede; # for short-lived callbacks, this reduces pressure on the coro pool
		569	}
		570	schedule; # sleep well
		571	}
		572	};
		573	$unblock_scheduler->desc ("[unblock_sub scheduler]");
		574
		575	sub unblock_sub(&) {
		576	my $cb = shift;
		577
		578	sub {
		579	unshift @unblock_queue, [$cb, @_];
		580	$unblock_scheduler->ready;
		581	}
		582	}
		583
		584	=back
		585
222	=cut	586	=cut
223		587
224	1;	588	1;
225		589
226	=head1 BUGS	590	=head1 BUGS/LIMITATIONS
227		591
228	- could be faster, especially when the core would introduce special	592	- you must make very sure that no coro is still active on global
229	support for coroutines (like it does for threads).	593	destruction. very bad things might happen otherwise (usually segfaults).
230	- there is still a memleak on coroutine termination that I could not	594
231	identify. Could be as small as a single SV.	595	- this module is not thread-safe. You should only ever use this module
232	- this module is not well-tested.	596	from the same thread (this requirement might be loosened in the future
		597	to allow per-thread schedulers, but Coro::State does not yet allow
		598	this).
233		599
234	=head1 SEE ALSO	600	=head1 SEE ALSO
235		601
236	L<Coro::Channel>, L<Coro::Cont>, L<Coro::Specific>, L<Coro::Semaphore>,	602	Support/Utility: L<Coro::Specific>, L<Coro::State>, L<Coro::Util>.
237	L<Coro::Signal>, L<Coro::State>, L<Coro::Event>.	603
		604	Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>.
		605
		606	Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::Select>.
		607
		608	Embedding: L<Coro:MakeMaker>
238		609
239	=head1 AUTHOR	610	=head1 AUTHOR
240		611
241	Marc Lehmann <pcg@goof.com>	612	Marc Lehmann <schmorp@schmorp.de>
242	http://www.goof.com/pcg/marc/	613	http://home.schmorp.de/
243		614
244	=cut	615	=cut
245		616

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.15 by root, Tue Jul 17 02:55:29 2001 UTC vs. Revision 1.148 by root, Fri Oct 5 20:11:25 2007 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.15 by root, Tue Jul 17 02:55:29 2001 UTC vs.
Revision 1.148 by root, Fri Oct 5 20:11:25 2007 UTC