[ViewVC] Diff of: cvs/AnyEvent-Fork/Fork.pm

Comparing AnyEvent-Fork/Fork.pm (file contents):
Revision 1.25 by root, Sat Apr 6 08:55:16 2013 UTC vs.
Revision 1.63 by root, Wed Nov 26 13:36:18 2014 UTC

…		…
27		27
28	Special care has been taken to make this module useful from other modules,	28	Special care has been taken to make this module useful from other modules,
29	while still supporting specialised environments such as L<App::Staticperl>	29	while still supporting specialised environments such as L<App::Staticperl>
30	or L<PAR::Packer>.	30	or L<PAR::Packer>.
31		31
32	=head1 WHAT THIS MODULE IS NOT	32	=head2 WHAT THIS MODULE IS NOT
33		33
34	This module only creates processes and lets you pass file handles and	34	This module only creates processes and lets you pass file handles and
35	strings to it, and run perl code. It does not implement any kind of RPC -	35	strings to it, and run perl code. It does not implement any kind of RPC -
36	there is no back channel from the process back to you, and there is no RPC	36	there is no back channel from the process back to you, and there is no RPC
37	or message passing going on.	37	or message passing going on.
38		38
39	If you need some form of RPC, you can either implement it yourself	39	If you need some form of RPC, you could use the L<AnyEvent::Fork::RPC>
40	in whatever way you like, use some message-passing module such	40	companion module, which adds simple RPC/job queueing to a process created
41	as L<AnyEvent::MP>, some pipe such as L<AnyEvent::ZeroMQ>, use	41	by this module.
42	L<AnyEvent::Handle> on both sides to send e.g. JSON or Storable messages,
43	and so on.
44		42
		43	And if you need some automatic process pool management on top of
		44	L<AnyEvent::Fork::RPC>, you can look at the L<AnyEvent::Fork::Pool>
		45	companion module.
		46
		47	Or you can implement it yourself in whatever way you like: use some
		48	message-passing module such as L<AnyEvent::MP>, some pipe such as
		49	L<AnyEvent::ZeroMQ>, use L<AnyEvent::Handle> on both sides to send
		50	e.g. JSON or Storable messages, and so on.
		51
		52	=head2 COMPARISON TO OTHER MODULES
		53
		54	There is an abundance of modules on CPAN that do "something fork", such as
		55	L<Parallel::ForkManager>, L<AnyEvent::ForkManager>, L<AnyEvent::Worker>
		56	or L<AnyEvent::Subprocess>. There are modules that implement their own
		57	process management, such as L<AnyEvent::DBI>.
		58
		59	The problems that all these modules try to solve are real, however, none
		60	of them (from what I have seen) tackle the very real problems of unwanted
		61	memory sharing, efficiency or not being able to use event processing, GUI
		62	toolkits or similar modules in the processes they create.
		63
		64	This module doesn't try to replace any of them - instead it tries to solve
		65	the problem of creating processes with a minimum of fuss and overhead (and
		66	also luxury). Ideally, most of these would use AnyEvent::Fork internally,
		67	except they were written before AnyEvent:Fork was available, so obviously
		68	had to roll their own.
		69
45	=head1 PROBLEM STATEMENT	70	=head2 PROBLEM STATEMENT
46		71
47	There are two traditional ways to implement parallel processing on UNIX	72	There are two traditional ways to implement parallel processing on UNIX
48	like operating systems - fork and process, and fork+exec and process. They	73	like operating systems - fork and process, and fork+exec and process. They
49	have different advantages and disadvantages that I describe below,	74	have different advantages and disadvantages that I describe below,
50	together with how this module tries to mitigate the disadvantages.	75	together with how this module tries to mitigate the disadvantages.
…		…
64		89
65	=item Forking usually creates a copy-on-write copy of the parent	90	=item Forking usually creates a copy-on-write copy of the parent
66	process.	91	process.
67		92
68	For example, modules or data files that are loaded will not use additional	93	For example, modules or data files that are loaded will not use additional
69	memory after a fork. When exec'ing a new process, modules and data files	94	memory after a fork. Exec'ing a new process, in contrast, means modules
70	might need to be loaded again, at extra CPU and memory cost. But when	95	and data files might need to be loaded again, at extra CPU and memory
71	forking, literally all data structures are copied - if the program frees	96	cost.
		97
		98	But when forking, you still create a copy of your data structures - if
72	them and replaces them by new data, the child processes will retain the	99	the program frees them and replaces them by new data, the child processes
73	old version even if it isn't used, which can suddenly and unexpectedly	100	will retain the old version even if it isn't used, which can suddenly and
74	increase memory usage when freeing memory.	101	unexpectedly increase memory usage when freeing memory.
75		102
		103	For example, L<Gtk2::CV> is an image viewer optimised for large
		104	directories (millions of pictures). It also forks subprocesses for
		105	thumbnail generation, which inherit the data structure that stores all
		106	file information. If the user changes the directory, it gets freed in
		107	the main process, leaving a copy in the thumbnailer processes. This can
		108	lead to many times the memory usage that would actually be required. The
		109	solution is to fork early (and being unable to dynamically generate more
		110	subprocesses or do this from a module)... or to use L<AnyEvent:Fork>.
		111
76	The trade-off is between more sharing with fork (which can be good or	112	There is a trade-off between more sharing with fork (which can be good or
77	bad), and no sharing with exec.	113	bad), and no sharing with exec.
78		114
79	This module allows the main program to do a controlled fork, and allows	115	This module allows the main program to do a controlled fork, and allows
80	modules to exec processes safely at any time. When creating a custom	116	modules to exec processes safely at any time. When creating a custom
81	process pool you can take advantage of data sharing via fork without	117	process pool you can take advantage of data sharing via fork without
…		…
86	shared and what isn't, at all times.	122	shared and what isn't, at all times.
87		123
88	=item Exec'ing a new perl process might be difficult.	124	=item Exec'ing a new perl process might be difficult.
89		125
90	For example, it is not easy to find the correct path to the perl	126	For example, it is not easy to find the correct path to the perl
91	interpreter - C<$^X> might not be a perl interpreter at all.	127	interpreter - C<$^X> might not be a perl interpreter at all. Worse, there
		128	might not even be a perl binary installed on the system.
92		129
93	This module tries hard to identify the correct path to the perl	130	This module tries hard to identify the correct path to the perl
94	interpreter. With a cooperative main program, exec'ing the interpreter	131	interpreter. With a cooperative main program, exec'ing the interpreter
95	might not even be necessary, but even without help from the main program,	132	might not even be necessary, but even without help from the main program,
96	it will still work when used from a module.	133	it will still work when used from a module.
…		…
102	and modules are no longer loadable because they refer to a different	139	and modules are no longer loadable because they refer to a different
103	perl version, or parts of a distribution are newer than the ones already	140	perl version, or parts of a distribution are newer than the ones already
104	loaded.	141	loaded.
105		142
106	This module supports creating pre-initialised perl processes to be used as	143	This module supports creating pre-initialised perl processes to be used as
107	a template for new processes.	144	a template for new processes at a later time, e.g. for use in a process
		145	pool.
108		146
109	=item Forking might be impossible when a program is running.	147	=item Forking might be impossible when a program is running.
110		148
111	For example, POSIX makes it almost impossible to fork from a	149	For example, POSIX makes it almost impossible to fork from a
112	multi-threaded program while doing anything useful in the child - in	150	multi-threaded program while doing anything useful in the child - in
113	fact, if your perl program uses POSIX threads (even indirectly via	151	fact, if your perl program uses POSIX threads (even indirectly via
114	e.g. L<IO::AIO> or L<threads>), you cannot call fork on the perl level	152	e.g. L<IO::AIO> or L<threads>), you cannot call fork on the perl level
115	anymore without risking corruption issues on a number of operating	153	anymore without risking memory corruption or worse on a number of
116	systems.	154	operating systems.
117		155
118	This module can safely fork helper processes at any time, by calling	156	This module can safely fork helper processes at any time, by calling
119	fork+exec in C, in a POSIX-compatible way (via L<Proc::FastSpawn>).	157	fork+exec in C, in a POSIX-compatible way (via L<Proc::FastSpawn>).
120		158
121	=item Parallel processing with fork might be inconvenient or difficult	159	=item Parallel processing with fork might be inconvenient or difficult
…		…
125	becomes very hard to use the event loop from a child program, as the	163	becomes very hard to use the event loop from a child program, as the
126	watchers already exist but are only meaningful in the parent. Worse, a	164	watchers already exist but are only meaningful in the parent. Worse, a
127	module might want to use such a module, not knowing whether another module	165	module might want to use such a module, not knowing whether another module
128	or the main program also does, leading to problems.	166	or the main program also does, leading to problems.
129		167
		168	Apart from event loops, graphical toolkits also commonly fall into the
		169	"unsafe module" category, or just about anything that communicates with
		170	the external world, such as network libraries and file I/O modules, which
		171	usually don't like being copied and then allowed to continue in two
		172	processes.
		173
130	With this module only the main program is allowed to create new processes	174	With this module only the main program is allowed to create new processes
131	by forking (because only the main program can know when it is still safe	175	by forking (because only the main program can know when it is still safe
132	to do so) - all other processes are created via fork+exec, which makes it	176	to do so) - all other processes are created via fork+exec, which makes it
133	possible to use modules such as event loops or window interfaces safely.	177	possible to use modules such as event loops or window interfaces safely.
134		178
…		…
146		190
147	# now $master_filehandle is connected to the	191	# now $master_filehandle is connected to the
148	# $slave_filehandle in the new process.	192	# $slave_filehandle in the new process.
149	});	193	});
150		194
151	# MyModule::worker might look like this	195	C<MyModule> might look like this:
		196
		197	package MyModule;
		198
152	sub MyModule::worker {	199	sub worker {
153	my ($slave_filehandle) = @_;	200	my ($slave_filehandle) = @_;
154		201
155	# now $slave_filehandle is connected to the $master_filehandle	202	# now $slave_filehandle is connected to the $master_filehandle
156	# in the original prorcess. have fun!	203	# in the original prorcess. have fun!
157	}	204	}
…		…
176	}	223	}
177		224
178	# now do other things - maybe use the filehandle provided by run	225	# now do other things - maybe use the filehandle provided by run
179	# to wait for the processes to die. or whatever.	226	# to wait for the processes to die. or whatever.
180		227
181	# My::Server::run might look like this	228	C<My::Server> might look like this:
182	sub My::Server::run {	229
		230	package My::Server;
		231
		232	sub run {
183	my ($slave, $listener, $id) = @_;	233	my ($slave, $listener, $id) = @_;
184		234
185	close $slave; # we do not use the socket, so close it to save resources	235	close $slave; # we do not use the socket, so close it to save resources
186		236
187	# we could go ballistic and use e.g. AnyEvent here, or IO::AIO,	237	# we could go ballistic and use e.g. AnyEvent here, or IO::AIO,
…		…
191	}	241	}
192	}	242	}
193		243
194	=head2 use AnyEvent::Fork as a faster fork+exec	244	=head2 use AnyEvent::Fork as a faster fork+exec
195		245
196	This runs /bin/echo hi, with stdout redirected to /tmp/log and stderr to	246	This runs C</bin/echo hi>, with standard output redirected to F</tmp/log>
197	the communications socket. It is usually faster than fork+exec, but still	247	and standard error redirected to the communications socket. It is usually
198	let's you prepare the environment.	248	faster than fork+exec, but still lets you prepare the environment.
199		249
200	open my $output, ">/tmp/log" or die "$!";	250	open my $output, ">/tmp/log" or die "$!";
201		251
202	AnyEvent::Fork	252	AnyEvent::Fork
203	->new	253	->new
204	->eval ('	254	->eval ('
		255	# compile a helper function for later use
205	sub run {	256	sub run {
206	my ($fh, $output, @cmd) = @_;	257	my ($fh, $output, @cmd) = @_;
207		258
208	# perl will clear close-on-exec on STDOUT/STDERR	259	# perl will clear close-on-exec on STDOUT/STDERR
209	open STDOUT, ">&", $output or die;	260	open STDOUT, ">&", $output or die;
…		…
216	->send_arg ("/bin/echo", "hi")	267	->send_arg ("/bin/echo", "hi")
217	->run ("run", my $cv = AE::cv);	268	->run ("run", my $cv = AE::cv);
218		269
219	my $stderr = $cv->recv;	270	my $stderr = $cv->recv;
220		271
		272	=head2 For stingy users: put the worker code into a C<DATA> section.
		273
		274	When you want to be stingy with files, you can put your code into the
		275	C<DATA> section of your module (or program):
		276
		277	use AnyEvent::Fork;
		278
		279	AnyEvent::Fork
		280	->new
		281	->eval (do { local $/; <DATA> })
		282	->run ("doit", sub { ... });
		283
		284	__DATA__
		285
		286	sub doit {
		287	... do something!
		288	}
		289
		290	=head2 For stingy standalone programs: do not rely on external files at
		291	all.
		292
		293	For single-file scripts it can be inconvenient to rely on external
		294	files - even when using a C<DATA> section, you still need to C<exec> an
		295	external perl interpreter, which might not be available when using
		296	L<App::Staticperl>, L<Urlader> or L<PAR::Packer> for example.
		297
		298	Two modules help here - L<AnyEvent::Fork::Early> forks a template process
		299	for all further calls to C<new_exec>, and L<AnyEvent::Fork::Template>
		300	forks the main program as a template process.
		301
		302	Here is how your main program should look like:
		303
		304	#! perl
		305
		306	# optional, as the very first thing.
		307	# in case modules want to create their own processes.
		308	use AnyEvent::Fork::Early;
		309
		310	# next, load all modules you need in your template process
		311	use Example::My::Module
		312	use Example::Whatever;
		313
		314	# next, put your run function definition and anything else you
		315	# need, but do not use code outside of BEGIN blocks.
		316	sub worker_run {
		317	my ($fh, @args) = @_;
		318	...
		319	}
		320
		321	# now preserve everything so far as AnyEvent::Fork object
		322	# in $TEMPLATE.
		323	use AnyEvent::Fork::Template;
		324
		325	# do not put code outside of BEGIN blocks until here
		326
		327	# now use the $TEMPLATE process in any way you like
		328
		329	# for example: create 10 worker processes
		330	my @worker;
		331	my $cv = AE::cv;
		332	for (1..10) {
		333	$cv->begin;
		334	$TEMPLATE->fork->send_arg ($_)->run ("worker_run", sub {
		335	push @worker, shift;
		336	$cv->end;
		337	});
		338	}
		339	$cv->recv;
		340
221	=head1 CONCEPTS	341	=head1 CONCEPTS
222		342
223	This module can create new processes either by executing a new perl	343	This module can create new processes either by executing a new perl
224	process, or by forking from an existing "template" process.	344	process, or by forking from an existing "template" process.
		345
		346	All these processes are called "child processes" (whether they are direct
		347	children or not), while the process that manages them is called the
		348	"parent process".
225		349
226	Each such process comes with its own file handle that can be used to	350	Each such process comes with its own file handle that can be used to
227	communicate with it (it's actually a socket - one end in the new process,	351	communicate with it (it's actually a socket - one end in the new process,
228	one end in the main process), and among the things you can do in it are	352	one end in the main process), and among the things you can do in it are
229	load modules, fork new processes, send file handles to it, and execute	353	load modules, fork new processes, send file handles to it, and execute
…		…
303	my ($fork_fh) = @_;	427	my ($fork_fh) = @_;
304	});	428	});
305		429
306	=back	430	=back
307		431
308	=head1 FUNCTIONS	432	=head1 THE C<AnyEvent::Fork> CLASS
		433
		434	This module exports nothing, and only implements a single class -
		435	C<AnyEvent::Fork>.
		436
		437	There are two class constructors that both create new processes - C<new>
		438	and C<new_exec>. The C<fork> method creates a new process by forking an
		439	existing one and could be considered a third constructor.
		440
		441	Most of the remaining methods deal with preparing the new process, by
		442	loading code, evaluating code and sending data to the new process. They
		443	usually return the process object, so you can chain method calls.
		444
		445	If a process object is destroyed before calling its C<run> method, then
		446	the process simply exits. After C<run> is called, all responsibility is
		447	passed to the specified function.
		448
		449	As long as there is any outstanding work to be done, process objects
		450	resist being destroyed, so there is no reason to store them unless you
		451	need them later - configure and forget works just fine.
309		452
310	=over 4	453	=over 4
311		454
312	=cut	455	=cut
313		456
…		…
320	use AnyEvent;	463	use AnyEvent;
321	use AnyEvent::Util ();	464	use AnyEvent::Util ();
322		465
323	use IO::FDPass;	466	use IO::FDPass;
324		467
325	our $VERSION = 0.5;	468	our $VERSION = 1.2;
326
327	our $PERL; # the path to the perl interpreter, deduces with various forms of magic
328
329	=item my $pool = new AnyEvent::Fork key => value...
330
331	Create a new process pool. The following named parameters are supported:
332
333	=over 4
334
335	=back
336
337	=cut
338		469
339	# the early fork template process	470	# the early fork template process
340	our $EARLY;	471	our $EARLY;
341		472
342	# the empty template process	473	# the empty template process
343	our $TEMPLATE;	474	our $TEMPLATE;
		475
		476	sub QUEUE() { 0 }
		477	sub FH() { 1 }
		478	sub WW() { 2 }
		479	sub PID() { 3 }
		480	sub CB() { 4 }
		481
		482	sub _new {
		483	my ($self, $fh, $pid) = @_;
		484
		485	AnyEvent::Util::fh_nonblocking $fh, 1;
		486
		487	$self = bless [
		488	[], # write queue - strings or fd's
		489	$fh,
		490	undef, # AE watcher
		491	$pid,
		492	], $self;
		493
		494	$self
		495	}
344		496
345	sub _cmd {	497	sub _cmd {
346	my $self = shift;	498	my $self = shift;
347		499
348	# ideally, we would want to use "a (w/a)*" as format string, but perl	500	# ideally, we would want to use "a (w/a)*" as format string, but perl
349	# versions from at least 5.8.9 to 5.16.3 are all buggy and can't unpack	501	# versions from at least 5.8.9 to 5.16.3 are all buggy and can't unpack
350	# it.	502	# it.
351	push @{ $self->[2] }, pack "a L/a*", $_[0], $_[1];	503	push @{ $self->[QUEUE] }, pack "a L/a*", $_[0], $_[1];
352		504
353	$self->[3] \|\|= AE::io $self->[1], 1, sub {	505	$self->[WW] \|\|= AE::io $self->[FH], 1, sub {
354	do {	506	do {
355	# send the next "thing" in the queue - either a reference to an fh,	507	# send the next "thing" in the queue - either a reference to an fh,
356	# or a plain string.	508	# or a plain string.
357		509
358	if (ref $self->[2][0]) {	510	if (ref $self->[QUEUE][0]) {
359	# send fh	511	# send fh
360	unless (IO::FDPass::send fileno $self->[1], fileno ${ $self->[2][0] }) {	512	unless (IO::FDPass::send fileno $self->[FH], fileno ${ $self->[QUEUE][0] }) {
361	return if $! == Errno::EAGAIN \|\| $! == Errno::EWOULDBLOCK;	513	return if $! == Errno::EAGAIN \|\| $! == Errno::EWOULDBLOCK;
362	undef $self->[3];	514	undef $self->[WW];
363	die "AnyEvent::Fork: file descriptor send failure: $!";	515	die "AnyEvent::Fork: file descriptor send failure: $!";
364	}	516	}
365		517
366	shift @{ $self->[2] };	518	shift @{ $self->[QUEUE] };
367		519
368	} else {	520	} else {
369	# send string	521	# send string
370	my $len = syswrite $self->[1], $self->[2][0];	522	my $len = syswrite $self->[FH], $self->[QUEUE][0];
371		523
372	unless ($len) {	524	unless ($len) {
373	return if $! == Errno::EAGAIN \|\| $! == Errno::EWOULDBLOCK;	525	return if $! == Errno::EAGAIN \|\| $! == Errno::EWOULDBLOCK;
374	undef $self->[3];	526	undef $self->[WW];
375	die "AnyEvent::Fork: command write failure: $!";	527	die "AnyEvent::Fork: command write failure: $!";
376	}	528	}
377		529
378	substr $self->[2][0], 0, $len, "";	530	substr $self->[QUEUE][0], 0, $len, "";
379	shift @{ $self->[2] } unless length $self->[2][0];	531	shift @{ $self->[QUEUE] } unless length $self->[QUEUE][0];
380	}	532	}
381	} while @{ $self->[2] };	533	} while @{ $self->[QUEUE] };
382		534
383	# everything written	535	# everything written
384	undef $self->[3];	536	undef $self->[WW];
385		537
386	# invoke run callback, if any	538	# invoke run callback, if any
387	$self->[4]->($self->[1]) if $self->[4];	539	if ($self->[CB]) {
		540	$self->[CB]->($self->[FH]);
		541	@$self = ();
		542	}
388	};	543	};
389		544
390	() # make sure we don't leak the watcher	545	() # make sure we don't leak the watcher
391	}
392
393	sub _new {
394	my ($self, $fh, $pid) = @_;
395
396	AnyEvent::Util::fh_nonblocking $fh, 1;
397
398	$self = bless [
399	$pid,
400	$fh,
401	[], # write queue - strings or fd's
402	undef, # AE watcher
403	], $self;
404
405	$self
406	}	546	}
407		547
408	# fork template from current process, used by AnyEvent::Fork::Early/Template	548	# fork template from current process, used by AnyEvent::Fork::Early/Template
409	sub _new_fork {	549	sub _new_fork {
410	my ($fh, $slave) = AnyEvent::Util::portable_socketpair;	550	my ($fh, $slave) = AnyEvent::Util::portable_socketpair;
…		…
415	if ($pid eq 0) {	555	if ($pid eq 0) {
416	require AnyEvent::Fork::Serve;	556	require AnyEvent::Fork::Serve;
417	$AnyEvent::Fork::Serve::OWNER = $parent;	557	$AnyEvent::Fork::Serve::OWNER = $parent;
418	close $fh;	558	close $fh;
419	$0 = "$_[1] of $parent";	559	$0 = "$_[1] of $parent";
420	$SIG{CHLD} = 'IGNORE';
421	AnyEvent::Fork::Serve::serve ($slave);	560	AnyEvent::Fork::Serve::serve ($slave);
422	exit 0;	561	exit 0;
423	} elsif (!$pid) {	562	} elsif (!$pid) {
424	die "AnyEvent::Fork::Early/Template: unable to fork template process: $!";	563	die "AnyEvent::Fork::Early/Template: unable to fork template process: $!";
425	}	564	}
…		…
432	Create a new "empty" perl interpreter process and returns its process	571	Create a new "empty" perl interpreter process and returns its process
433	object for further manipulation.	572	object for further manipulation.
434		573
435	The new process is forked from a template process that is kept around	574	The new process is forked from a template process that is kept around
436	for this purpose. When it doesn't exist yet, it is created by a call to	575	for this purpose. When it doesn't exist yet, it is created by a call to
437	C<new_exec> and kept around for future calls.	576	C<new_exec> first and then stays around for future calls.
438
439	When the process object is destroyed, it will release the file handle
440	that connects it with the new process. When the new process has not yet
441	called C<run>, then the process will exit. Otherwise, what happens depends
442	entirely on the code that is executed.
443		577
444	=cut	578	=cut
445		579
446	sub new {	580	sub new {
447	my $class = shift;	581	my $class = shift;
…		…
484		618
485	You should use C<new> whenever possible, except when having a template	619	You should use C<new> whenever possible, except when having a template
486	process around is unacceptable.	620	process around is unacceptable.
487		621
488	The path to the perl interpreter is divined using various methods - first	622	The path to the perl interpreter is divined using various methods - first
489	C<$^X> is investigated to see if the path ends with something that sounds	623	C<$^X> is investigated to see if the path ends with something that looks
490	as if it were the perl interpreter. Failing this, the module falls back to	624	as if it were the perl interpreter. Failing this, the module falls back to
491	using C<$Config::Config{perlpath}>.	625	using C<$Config::Config{perlpath}>.
492		626
		627	The path to perl can also be overriden by setting the global variable
		628	C<$AnyEvent::Fork::PERL> - it's value will be used for all subsequent
		629	invocations.
		630
493	=cut	631	=cut
		632
		633	our $PERL;
494		634
495	sub new_exec {	635	sub new_exec {
496	my ($self) = @_;	636	my ($self) = @_;
497		637
498	return $EARLY->fork	638	return $EARLY->fork
499	if $EARLY;	639	if $EARLY;
500		640
		641	unless (defined $PERL) {
501	# first find path of perl	642	# first find path of perl
502	my $perl = $;	643	my $perl = $^X;
503		644
504	# first we try $^X, but the path must be absolute (always on win32), and end in sth.	645	# first we try $^X, but the path must be absolute (always on win32), and end in sth.
505	# that looks like perl. this obviously only works for posix and win32	646	# that looks like perl. this obviously only works for posix and win32
506	unless (	647	unless (
507	($^O eq "MSWin32" \|\| $perl =~ m%^/%)	648	($^O eq "MSWin32" \|\| $perl =~ m%^/%)
508	&& $perl =~ m%[/\\]perl(?:[0-9]+(\.[0-9]+)+)?(\.exe)?$%i	649	&& $perl =~ m%[/\\]perl(?:[0-9]+(\.[0-9]+)+)?(\.exe)?$%i
509	) {	650	) {
510	# if it doesn't look perlish enough, try Config	651	# if it doesn't look perlish enough, try Config
511	require Config;	652	require Config;
512	$perl = $Config::Config{perlpath};	653	$perl = $Config::Config{perlpath};
513	$perl =~ s/(?:\Q$Config::Config{_exe}\E)?$/$Config::Config{_exe}/;	654	$perl =~ s/(?:\Q$Config::Config{_exe}\E)?$/$Config::Config{_exe}/;
		655	}
		656
		657	$PERL = $perl;
514	}	658	}
515		659
516	require Proc::FastSpawn;	660	require Proc::FastSpawn;
517		661
518	my ($fh, $slave) = AnyEvent::Util::portable_socketpair;	662	my ($fh, $slave) = AnyEvent::Util::portable_socketpair;
…		…
526	#local $ENV{PERL5LIB} = join ":", grep !ref, @INC;	670	#local $ENV{PERL5LIB} = join ":", grep !ref, @INC;
527	my %env = %ENV;	671	my %env = %ENV;
528	$env{PERL5LIB} = join +($^O eq "MSWin32" ? ";" : ":"), grep !ref, @INC;	672	$env{PERL5LIB} = join +($^O eq "MSWin32" ? ";" : ":"), grep !ref, @INC;
529		673
530	my $pid = Proc::FastSpawn::spawn (	674	my $pid = Proc::FastSpawn::spawn (
531	$perl,	675	$PERL,
532	["perl", "-MAnyEvent::Fork::Serve", "-e", "AnyEvent::Fork::Serve::me", fileno $slave, $$],	676	["perl", "-MAnyEvent::Fork::Serve", "-e", "AnyEvent::Fork::Serve::me", fileno $slave, $$],
533	[map "$_=$env{$_}", keys %env],	677	[map "$_=$env{$_}", keys %env],
534	) or die "unable to spawn AnyEvent::Fork server: $!";	678	) or die "unable to spawn AnyEvent::Fork server: $!";
535		679
536	$self->_new ($fh, $pid)	680	$self->_new ($fh, $pid)
537	}	681	}
538		682
539	=item $pid = $proc->pid	683	=item $pid = $proc->pid
540		684
541	Returns the process id of the process I<iff it is a direct child of the	685	Returns the process id of the process I<iff it is a direct child of the
542	process> running AnyEvent::Fork, and C<undef> otherwise.	686	process running AnyEvent::Fork>, and C<undef> otherwise. As a general
		687	rule (that you cannot rely upon), processes created via C<new_exec>,
		688	L<AnyEvent::Fork::Early> or L<AnyEvent::Fork::Template> are direct
		689	children, while all other processes are not.
543		690
544	Normally, only processes created via C<< AnyEvent::Fork->new_exec >> and	691	Or in other words, you do not normally have to take care of zombies for
545	L<AnyEvent::Fork::Template> are direct children, and you are responsible	692	processes created via C<new>, but when in doubt, or zombies are a problem,
546	to clean up their zombies when they die.	693	you need to check whether a process is a diretc child by calling this
547		694	method, and possibly creating a child watcher or reap it manually.
548	All other processes are not direct children, and will be cleaned up by
549	AnyEvent::Fork.
550		695
551	=cut	696	=cut
552		697
553	sub pid {	698	sub pid {
554	$_[0][0]	699	$_[0][PID]
555	}	700	}
556		701
557	=item $proc = $proc->eval ($perlcode, @args)	702	=item $proc = $proc->eval ($perlcode, @args)
558		703
559	Evaluates the given C<$perlcode> as ... perl code, while setting C<@_> to	704	Evaluates the given C<$perlcode> as ... Perl code, while setting C<@_> to
560	the strings specified by C<@args>, in the "main" package.	705	the strings specified by C<@args>, in the "main" package.
561		706
562	This call is meant to do any custom initialisation that might be required	707	This call is meant to do any custom initialisation that might be required
563	(for example, the C<require> method uses it). It's not supposed to be used	708	(for example, the C<require> method uses it). It's not supposed to be used
564	to completely take over the process, use C<run> for that.	709	to completely take over the process, use C<run> for that.
565		710
566	The code will usually be executed after this call returns, and there is no	711	The code will usually be executed after this call returns, and there is no
567	way to pass anything back to the calling process. Any evaluation errors	712	way to pass anything back to the calling process. Any evaluation errors
568	will be reported to stderr and cause the process to exit.	713	will be reported to stderr and cause the process to exit.
569		714
570	If you want to execute some code to take over the process (see the	715	If you want to execute some code (that isn't in a module) to take over the
571	"fork+exec" example in the SYNOPSIS), you should compile a function via	716	process, you should compile a function via C<eval> first, and then call
572	C<eval> first, and then call it via C<run>. This also gives you access to	717	it via C<run>. This also gives you access to any arguments passed via the
573	any arguments passed via the C<send_xxx> methods, such as file handles.	718	C<send_xxx> methods, such as file handles. See the L<use AnyEvent::Fork as
		719	a faster fork+exec> example to see it in action.
574		720
575	Returns the process object for easy chaining of method calls.	721	Returns the process object for easy chaining of method calls.
576		722
577	=cut	723	=cut
578		724
…		…
604	=item $proc = $proc->send_fh ($handle, ...)	750	=item $proc = $proc->send_fh ($handle, ...)
605		751
606	Send one or more file handles (I<not> file descriptors) to the process,	752	Send one or more file handles (I<not> file descriptors) to the process,
607	to prepare a call to C<run>.	753	to prepare a call to C<run>.
608		754
609	The process object keeps a reference to the handles until this is done,	755	The process object keeps a reference to the handles until they have
610	so you must not explicitly close the handles. This is most easily	756	been passed over to the process, so you must not explicitly close the
611	accomplished by simply not storing the file handles anywhere after passing	757	handles. This is most easily accomplished by simply not storing the file
612	them to this method.	758	handles anywhere after passing them to this method - when AnyEvent::Fork
		759	is finished using them, perl will automatically close them.
613		760
614	Returns the process object for easy chaining of method calls.	761	Returns the process object for easy chaining of method calls.
615		762
616	Example: pass a file handle to a process, and release it without	763	Example: pass a file handle to a process, and release it without
617	closing. It will be closed automatically when it is no longer used.	764	closing. It will be closed automatically when it is no longer used.
…		…
624	sub send_fh {	771	sub send_fh {
625	my ($self, @fh) = @_;	772	my ($self, @fh) = @_;
626		773
627	for my $fh (@fh) {	774	for my $fh (@fh) {
628	$self->_cmd ("h");	775	$self->_cmd ("h");
629	push @{ $self->[2] }, \$fh;	776	push @{ $self->[QUEUE] }, \$fh;
630	}	777	}
631		778
632	$self	779	$self
633	}	780	}
634		781
635	=item $proc = $proc->send_arg ($string, ...)	782	=item $proc = $proc->send_arg ($string, ...)
636		783
637	Send one or more argument strings to the process, to prepare a call to	784	Send one or more argument strings to the process, to prepare a call to
638	C<run>. The strings can be any octet string.	785	C<run>. The strings can be any octet strings.
639		786
640	The protocol is optimised to pass a moderate number of relatively short	787	The protocol is optimised to pass a moderate number of relatively short
641	strings - while you can pass up to 4GB of data in one go, this is more	788	strings - while you can pass up to 4GB of data in one go, this is more
642	meant to pass some ID information or other startup info, not big chunks of	789	meant to pass some ID information or other startup info, not big chunks of
643	data.	790	data.
…		…
659	Enter the function specified by the function name in C<$func> in the	806	Enter the function specified by the function name in C<$func> in the
660	process. The function is called with the communication socket as first	807	process. The function is called with the communication socket as first
661	argument, followed by all file handles and string arguments sent earlier	808	argument, followed by all file handles and string arguments sent earlier
662	via C<send_fh> and C<send_arg> methods, in the order they were called.	809	via C<send_fh> and C<send_arg> methods, in the order they were called.
663		810
		811	The process object becomes unusable on return from this function - any
		812	further method calls result in undefined behaviour.
		813
664	The function name should be fully qualified, but if it isn't, it will be	814	The function name should be fully qualified, but if it isn't, it will be
665	looked up in the main package.	815	looked up in the C<main> package.
666		816
667	If the called function returns, doesn't exist, or any error occurs, the	817	If the called function returns, doesn't exist, or any error occurs, the
668	process exits.	818	process exits.
669		819
670	Preparing the process is done in the background - when all commands have	820	Preparing the process is done in the background - when all commands have
671	been sent, the callback is invoked with the local communications socket	821	been sent, the callback is invoked with the local communications socket
672	as argument. At this point you can start using the socket in any way you	822	as argument. At this point you can start using the socket in any way you
673	like.	823	like.
674		824
675	The process object becomes unusable on return from this function - any
676	further method calls result in undefined behaviour.
677
678	If the communication socket isn't used, it should be closed on both sides,	825	If the communication socket isn't used, it should be closed on both sides,
679	to save on kernel memory.	826	to save on kernel memory.
680		827
681	The socket is non-blocking in the parent, and blocking in the newly	828	The socket is non-blocking in the parent, and blocking in the newly
682	created process. The close-on-exec flag is set in both.	829	created process. The close-on-exec flag is set in both.
683		830
684	Even if not used otherwise, the socket can be a good indicator for the	831	Even if not used otherwise, the socket can be a good indicator for the
685	existence of the process - if the other process exits, you get a readable	832	existence of the process - if the other process exits, you get a readable
686	event on it, because exiting the process closes the socket (if it didn't	833	event on it, because exiting the process closes the socket (if it didn't
687	create any children using fork).	834	create any children using fork).
		835
		836	=over 4
		837
		838	=item Compatibility to L<AnyEvent::Fork::Remote>
		839
		840	If you want to write code that works with both this module and
		841	L<AnyEvent::Fork::Remote>, you need to write your code so that it assumes
		842	there are two file handles for communications, which might not be unix
		843	domain sockets. The C<run> function should start like this:
		844
		845	sub run {
		846	my ($rfh, @args) = @_; # @args is your normal arguments
		847	my $wfh = fileno $rfh ? $rfh : *STDOUT;
		848
		849	# now use $rfh for reading and $wfh for writing
		850	}
		851
		852	This checks whether the passed file handle is, in fact, the process
		853	C<STDIN> handle. If it is, then the function was invoked visa
		854	L<AnyEvent::Fork::Remote>, so STDIN should be used for reading and
		855	C<STDOUT> should be used for writing.
		856
		857	In all other cases, the function was called via this module, and there is
		858	only one file handle that should be sued for reading and writing.
		859
		860	=back
688		861
689	Example: create a template for a process pool, pass a few strings, some	862	Example: create a template for a process pool, pass a few strings, some
690	file handles, then fork, pass one more string, and run some code.	863	file handles, then fork, pass one more string, and run some code.
691		864
692	my $pool = AnyEvent::Fork	865	my $pool = AnyEvent::Fork
…		…
720	=cut	893	=cut
721		894
722	sub run {	895	sub run {
723	my ($self, $func, $cb) = @_;	896	my ($self, $func, $cb) = @_;
724		897
725	$self->[4] = $cb;	898	$self->[CB] = $cb;
726	$self->_cmd (r => $func);	899	$self->_cmd (r => $func);
		900	}
		901
		902	=back
		903
		904	=head2 EXPERIMENTAL METHODS
		905
		906	These methods might go away completely or change behaviour, at any time.
		907
		908	=over 4
		909
		910	=item $proc->to_fh ($cb->($fh)) # EXPERIMENTAL, MIGHT BE REMOVED
		911
		912	Flushes all commands out to the process and then calls the callback with
		913	the communications socket.
		914
		915	The process object becomes unusable on return from this function - any
		916	further method calls result in undefined behaviour.
		917
		918	The point of this method is to give you a file handle that you can pass
		919	to another process. In that other process, you can call C<new_from_fh
		920	AnyEvent::Fork $fh> to create a new C<AnyEvent::Fork> object from it,
		921	thereby effectively passing a fork object to another process.
		922
		923	=cut
		924
		925	sub to_fh {
		926	my ($self, $cb) = @_;
		927
		928	$self->[CB] = $cb;
		929
		930	unless ($self->[WW]) {
		931	$self->[CB]->($self->[FH]);
		932	@$self = ();
		933	}
		934	}
		935
		936	=item new_from_fh AnyEvent::Fork $fh # EXPERIMENTAL, MIGHT BE REMOVED
		937
		938	Takes a file handle originally rceeived by the C<to_fh> method and creates
		939	a new C<AnyEvent:Fork> object. The child process itself will not change in
		940	any way, i.e. it will keep all the modifications done to it before calling
		941	C<to_fh>.
		942
		943	The new object is very much like the original object, except that the
		944	C<pid> method will return C<undef> even if the process is a direct child.
		945
		946	=cut
		947
		948	sub new_from_fh {
		949	my ($class, $fh) = @_;
		950
		951	$class->_new ($fh)
727	}	952	}
728		953
729	=back	954	=back
730		955
731	=head1 PERFORMANCE	956	=head1 PERFORMANCE
…		…
741		966
742	2079 new processes per second, using manual socketpair + fork	967	2079 new processes per second, using manual socketpair + fork
743		968
744	Then I did the same thing, but instead of calling fork, I called	969	Then I did the same thing, but instead of calling fork, I called
745	AnyEvent::Fork->new->run ("CORE::exit") and then again waited for the	970	AnyEvent::Fork->new->run ("CORE::exit") and then again waited for the
746	socket form the child to close on exit. This does the same thing as manual	971	socket from the child to close on exit. This does the same thing as manual
747	socket pair + fork, except that what is forked is the template process	972	socket pair + fork, except that what is forked is the template process
748	(2440kB), and the socket needs to be passed to the server at the other end	973	(2440kB), and the socket needs to be passed to the server at the other end
749	of the socket first.	974	of the socket first.
750		975
751	2307 new processes per second, using AnyEvent::Fork->new	976	2307 new processes per second, using AnyEvent::Fork->new
…		…
756	479 vfork+execs per second, using AnyEvent::Fork->new_exec	981	479 vfork+execs per second, using AnyEvent::Fork->new_exec
757		982
758	So how can C<< AnyEvent->new >> be faster than a standard fork, even	983	So how can C<< AnyEvent->new >> be faster than a standard fork, even
759	though it uses the same operations, but adds a lot of overhead?	984	though it uses the same operations, but adds a lot of overhead?
760		985
761	The difference is simply the process size: forking the 6MB process takes	986	The difference is simply the process size: forking the 5MB process takes
762	so much longer than forking the 2.5MB template process that the overhead	987	so much longer than forking the 2.5MB template process that the extra
763	introduced is canceled out.	988	overhead is canceled out.
764		989
765	If the benchmark process grows, the normal fork becomes even slower:	990	If the benchmark process grows, the normal fork becomes even slower:
766		991
767	1340 new processes, manual fork in a 20MB process	992	1340 new processes, manual fork of a 20MB process
768	731 new processes, manual fork in a 200MB process	993	731 new processes, manual fork of a 200MB process
769	235 new processes, manual fork in a 2000MB process	994	235 new processes, manual fork of a 2000MB process
770		995
771	What that means (to me) is that I can use this module without having a	996	What that means (to me) is that I can use this module without having a bad
772	very bad conscience because of the extra overhead required to start new	997	conscience because of the extra overhead required to start new processes.
773	processes.
774		998
775	=head1 TYPICAL PROBLEMS	999	=head1 TYPICAL PROBLEMS
776		1000
777	This section lists typical problems that remain. I hope by recognising	1001	This section lists typical problems that remain. I hope by recognising
778	them, most can be avoided.	1002	them, most can be avoided.
779		1003
780	=over 4	1004	=over 4
781		1005
782	=item "leaked" file descriptors for exec'ed processes	1006	=item leaked file descriptors for exec'ed processes
783		1007
784	POSIX systems inherit file descriptors by default when exec'ing a new	1008	POSIX systems inherit file descriptors by default when exec'ing a new
785	process. While perl itself laudably sets the close-on-exec flags on new	1009	process. While perl itself laudably sets the close-on-exec flags on new
786	file handles, most C libraries don't care, and even if all cared, it's	1010	file handles, most C libraries don't care, and even if all cared, it's
787	often not possible to set the flag in a race-free manner.	1011	often not possible to set the flag in a race-free manner.
…		…
807	libraries or the code that leaks those file descriptors.	1031	libraries or the code that leaks those file descriptors.
808		1032
809	Fortunately, most of these leaked descriptors do no harm, other than	1033	Fortunately, most of these leaked descriptors do no harm, other than
810	sitting on some resources.	1034	sitting on some resources.
811		1035
812	=item "leaked" file descriptors for fork'ed processes	1036	=item leaked file descriptors for fork'ed processes
813		1037
814	Normally, L<AnyEvent::Fork> does start new processes by exec'ing them,	1038	Normally, L<AnyEvent::Fork> does start new processes by exec'ing them,
815	which closes file descriptors not marked for being inherited.	1039	which closes file descriptors not marked for being inherited.
816		1040
817	However, L<AnyEvent::Fork::Early> and L<AnyEvent::Fork::Template> offer	1041	However, L<AnyEvent::Fork::Early> and L<AnyEvent::Fork::Template> offer
…		…
826		1050
827	The solution is to either not load these modules before use'ing	1051	The solution is to either not load these modules before use'ing
828	L<AnyEvent::Fork::Early> or L<AnyEvent::Fork::Template>, or to delay	1052	L<AnyEvent::Fork::Early> or L<AnyEvent::Fork::Template>, or to delay
829	initialising them, for example, by calling C<init Gtk2> manually.	1053	initialising them, for example, by calling C<init Gtk2> manually.
830		1054
831	=item exit runs destructors	1055	=item exiting calls object destructors
832		1056
833	This only applies to users of Lc<AnyEvent::Fork:Early> and	1057	This only applies to users of L<AnyEvent::Fork:Early> and
834	L<AnyEvent::Fork::Template>.	1058	L<AnyEvent::Fork::Template>, or when initialising code creates objects
		1059	that reference external resources.
835		1060
836	When a process created by AnyEvent::Fork exits, it might do so by calling	1061	When a process created by AnyEvent::Fork exits, it might do so by calling
837	exit, or simply letting perl reach the end of the program. At which point	1062	exit, or simply letting perl reach the end of the program. At which point
838	Perl runs all destructors.	1063	Perl runs all destructors.
839		1064
…		…
858	to make it so, mostly due to the bloody broken perl that nobody seems to	1083	to make it so, mostly due to the bloody broken perl that nobody seems to
859	care about. The fork emulation is a bad joke - I have yet to see something	1084	care about. The fork emulation is a bad joke - I have yet to see something
860	useful that you can do with it without running into memory corruption	1085	useful that you can do with it without running into memory corruption
861	issues or other braindamage. Hrrrr.	1086	issues or other braindamage. Hrrrr.
862		1087
863	Cygwin perl is not supported at the moment, as it should implement fd	1088	Since fork is endlessly broken on win32 perls (it doesn't even remotely
864	passing, but doesn't, and rolling my own is hard, as cygwin doesn't	1089	work within it's documented limits) and quite obviously it's not getting
865	support enough functionality to do it.	1090	improved any time soon, the best way to proceed on windows would be to
		1091	always use C<new_exec> and thus never rely on perl's fork "emulation".
		1092
		1093	Cygwin perl is not supported at the moment due to some hilarious
		1094	shortcomings of its API - see L<IO::FDPoll> for more details. If you never
		1095	use C<send_fh> and always use C<new_exec> to create processes, it should
		1096	work though.
		1097
		1098	=head1 USING AnyEvent::Fork IN SUBPROCESSES
		1099
		1100	AnyEvent::Fork itself cannot generally be used in subprocesses. As long as
		1101	only one process ever forks new processes, sharing the template processes
		1102	is possible (you could use a pipe as a lock by writing a byte into it to
		1103	unlock, and reading the byte to lock for example)
		1104
		1105	To make concurrent calls possible after fork, you should get rid of the
		1106	template and early fork processes. AnyEvent::Fork will create a new
		1107	template process as needed.
		1108
		1109	undef $AnyEvent::Fork::EARLY;
		1110	undef $AnyEvent::Fork::TEMPLATE;
		1111
		1112	It doesn't matter whether you get rid of them in the parent or child after
		1113	a fork.
866		1114
867	=head1 SEE ALSO	1115	=head1 SEE ALSO
868		1116
869	L<AnyEvent::Fork::Early> (to avoid executing a perl interpreter),	1117	L<AnyEvent::Fork::Early>, to avoid executing a perl interpreter at all
		1118	(part of this distribution).
		1119
870	L<AnyEvent::Fork::Template> (to create a process by forking the main	1120	L<AnyEvent::Fork::Template>, to create a process by forking the main
871	program at a convenient time).	1121	program at a convenient time (part of this distribution).
872		1122
873	=head1 AUTHOR	1123	L<AnyEvent::Fork::Remote>, for another way to create processes that is
		1124	mostly compatible to this module and modules building on top of it, but
		1125	works better with remote processes.
		1126
		1127	L<AnyEvent::Fork::RPC>, for simple RPC to child processes (on CPAN).
		1128
		1129	L<AnyEvent::Fork::Pool>, for simple worker process pool (on CPAN).
		1130
		1131	=head1 AUTHOR AND CONTACT INFORMATION
874		1132
875	Marc Lehmann <schmorp@schmorp.de>	1133	Marc Lehmann <schmorp@schmorp.de>
876	http://home.schmorp.de/	1134	http://software.schmorp.de/pkg/AnyEvent-Fork
877		1135
878	=cut	1136	=cut
879		1137
880	1	1138	1
881		1139

Diff Legend

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

Comparing AnyEvent-Fork/Fork.pm (file contents): Revision 1.25 by root, Sat Apr 6 08:55:16 2013 UTC vs. Revision 1.63 by root, Wed Nov 26 13:36:18 2014 UTC

Diff Legend

Comparing AnyEvent-Fork/Fork.pm (file contents):
Revision 1.25 by root, Sat Apr 6 08:55:16 2013 UTC vs.
Revision 1.63 by root, Wed Nov 26 13:36:18 2014 UTC