[ViewVC] Diff of: cvs/IO-AIO/AIO.pm

Comparing IO-AIO/AIO.pm (file contents):
Revision 1.25 by root, Sun Jul 31 21:21:12 2005 UTC vs.
Revision 1.39 by root, Sun Aug 28 11:05:50 2005 UTC

…		…
63	use base 'Exporter';	63	use base 'Exporter';
64		64
65	use Fcntl ();	65	use Fcntl ();
66		66
67	BEGIN {	67	BEGIN {
68	$VERSION = 1.1;	68	$VERSION = 1.6;
69		69
70	@EXPORT = qw(aio_read aio_write aio_open aio_close aio_stat aio_lstat aio_unlink	70	@EXPORT = qw(aio_sendfile aio_read aio_write aio_open aio_close aio_stat
		71	aio_lstat aio_unlink aio_rmdir aio_readdir aio_symlink
71	aio_fsync aio_fdatasync aio_readahead);	72	aio_fsync aio_fdatasync aio_readahead);
72	@EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel max_outstanding nreqs);	73	@EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel
		74	max_outstanding nreqs);
73		75
74	require XSLoader;	76	require XSLoader;
75	XSLoader::load IO::AIO, $VERSION;	77	XSLoader::load IO::AIO, $VERSION;
76	}	78	}
77		79
…		…
88	syscall has been executed asynchronously.	90	syscall has been executed asynchronously.
89		91
90	All functions expecting a filehandle keep a copy of the filehandle	92	All functions expecting a filehandle keep a copy of the filehandle
91	internally until the request has finished.	93	internally until the request has finished.
92		94
93	The filenames you pass to these routines I<must> be absolute. The reason	95	The pathnames you pass to these routines I<must> be absolute and
94	for this is that at the time the request is being executed, the current	96	encoded in byte form. The reason for the former is that at the time the
95	working directory could have changed. Alternatively, you can make sure	97	request is being executed, the current working directory could have
96	that you never change the current working directory.	98	changed. Alternatively, you can make sure that you never change the
		99	current working directory.
		100
		101	To encode pathnames to byte form, either make sure you either: a)
		102	always pass in filenames you got from outside (command line, readdir
		103	etc.), b) are ASCII or ISO 8859-1, c) use the Encode module and encode
		104	your pathnames to the locale (or other) encoding in effect in the user
		105	environment, d) use Glib::filename_from_unicode on unicode filenames or e)
		106	use something else.
97		107
98	=over 4	108	=over 4
99		109
100	=item aio_open $pathname, $flags, $mode, $callback	110	=item aio_open $pathname, $flags, $mode, $callback
101		111
…		…
142	Reads or writes C<length> bytes from the specified C<fh> and C<offset>	152	Reads or writes C<length> bytes from the specified C<fh> and C<offset>
143	into the scalar given by C<data> and offset C<dataoffset> and calls the	153	into the scalar given by C<data> and offset C<dataoffset> and calls the
144	callback without the actual number of bytes read (or -1 on error, just	154	callback without the actual number of bytes read (or -1 on error, just
145	like the syscall).	155	like the syscall).
146		156
		157	The C<$data> scalar I<MUST NOT> be modified in any way while the request
		158	is outstanding. Modifying it can result in segfaults or WW3 (if the
		159	necessary/optional hardware is installed).
		160
147	Example: Read 15 bytes at offset 7 into scalar C<$buffer>, starting at	161	Example: Read 15 bytes at offset 7 into scalar C<$buffer>, starting at
148	offset C<0> within the scalar:	162	offset C<0> within the scalar:
149		163
150	aio_read $fh, 7, 15, $buffer, 0, sub {	164	aio_read $fh, 7, 15, $buffer, 0, sub {
151	$_[0] > 0 or die "read error: $!";	165	$_[0] > 0 or die "read error: $!";
152	print "read $_[0] bytes: <$buffer>\n";	166	print "read $_[0] bytes: <$buffer>\n";
153	};	167	};
154		168
		169	=item aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback
		170
		171	Tries to copy C<$length> bytes from C<$in_fh> to C<$out_fh>. It starts
		172	reading at byte offset C<$in_offset>, and starts writing at the current
		173	file offset of C<$out_fh>. Because of that, it is not safe to issue more
		174	than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each
		175	other.
		176
		177	This call tries to make use of a native C<sendfile> syscall to provide
		178	zero-copy operation. For this to work, C<$out_fh> should refer to a
		179	socket, and C<$in_fh> should refer to mmap'able file.
		180
		181	If the native sendfile call fails or is not implemented, it will be
		182	emulated, so you can call C<aio_sendfile> on any type of filehandle
		183	regardless of the limitations of the operating system.
		184
		185	Please note, however, that C<aio_sendfile> can read more bytes from
		186	C<$in_fh> than are written, and there is no way to find out how many
		187	bytes have been read from C<aio_sendfile> alone, as C<aio_sendfile> only
		188	provides the number of bytes written to C<$out_fh>. Only if the result
		189	value equals C<$length> one can assume that C<$length> bytes have been
		190	read.
		191
155	=item aio_readahead $fh,$offset,$length, $callback	192	=item aio_readahead $fh,$offset,$length, $callback
156
157	Asynchronously reads the specified byte range into the page cache, using
158	the C<readahead> syscall. If that syscall doesn't exist (likely if your OS
159	isn't Linux) the status will be C<-1> and C<$!> is set to C<ENOSYS>.
160		193
161	C<aio_readahead> populates the page cache with data from a file so that	194	C<aio_readahead> populates the page cache with data from a file so that
162	subsequent reads from that file will not block on disk I/O. The C<$offset>	195	subsequent reads from that file will not block on disk I/O. The C<$offset>
163	argument specifies the starting point from which data is to be read and	196	argument specifies the starting point from which data is to be read and
164	C<$length> specifies the number of bytes to be read. I/O is performed in	197	C<$length> specifies the number of bytes to be read. I/O is performed in
165	whole pages, so that offset is effectively rounded down to a page boundary	198	whole pages, so that offset is effectively rounded down to a page boundary
166	and bytes are read up to the next page boundary greater than or equal to	199	and bytes are read up to the next page boundary greater than or equal to
167	(off-set+length). C<aio_readahead> does not read beyond the end of the	200	(off-set+length). C<aio_readahead> does not read beyond the end of the
168	file. The current file offset of the file is left unchanged.	201	file. The current file offset of the file is left unchanged.
169		202
		203	If that syscall doesn't exist (likely if your OS isn't Linux) it will be
		204	emulated by simply reading the data, which would have a similar effect.
		205
170	=item aio_stat $fh_or_path, $callback	206	=item aio_stat $fh_or_path, $callback
171		207
172	=item aio_lstat $fh, $callback	208	=item aio_lstat $fh, $callback
173		209
174	Works like perl's C<stat> or C<lstat> in void context. The callback will	210	Works like perl's C<stat> or C<lstat> in void context. The callback will
…		…
192	=item aio_unlink $pathname, $callback	228	=item aio_unlink $pathname, $callback
193		229
194	Asynchronously unlink (delete) a file and call the callback with the	230	Asynchronously unlink (delete) a file and call the callback with the
195	result code.	231	result code.
196		232
		233	=item aio_rmdir $pathname, $callback
		234
		235	Asynchronously rmdir (delete) a directory and call the callback with the
		236	result code.
		237
		238	=item aio_readdir $pathname $callback
		239
		240	Unlike the POSIX call of the same name, C<aio_readdir> reads an entire
		241	directory (i.e. opendir + readdir + closedir). The entries will not be
		242	sorted, and will B<NOT> include the C<.> and C<..> entries.
		243
		244	The callback a single argument which is either C<undef> or an array-ref
		245	with the filenames.
		246
197	=item aio_fsync $fh, $callback	247	=item aio_fsync $fh, $callback
198		248
199	Asynchronously call fsync on the given filehandle and call the callback	249	Asynchronously call fsync on the given filehandle and call the callback
200	with the fsync result code.	250	with the fsync result code.
201		251
202	=item aio_fdatasync $fh, $callback	252	=item aio_fdatasync $fh, $callback
203		253
204	Asynchronously call fdatasync on the given filehandle and call the	254	Asynchronously call fdatasync on the given filehandle and call the
205	callback with the fdatasync result code. Might set C<$!> to C<ENOSYS> if	255	callback with the fdatasync result code.
206	C<fdatasync> is not available.	256
		257	If this call isn't available because your OS lacks it or it couldn't be
		258	detected, it will be emulated by calling C<fsync> instead.
207		259
208	=back	260	=back
209		261
210	=head2 SUPPORT FUNCTIONS	262	=head2 SUPPORT FUNCTIONS
211		263
…		…
269	IO::AIO::poll_wait, IO::AIO::poll_cb	321	IO::AIO::poll_wait, IO::AIO::poll_cb
270	if IO::AIO::nreqs;	322	if IO::AIO::nreqs;
271		323
272	=item IO::AIO::min_parallel $nthreads	324	=item IO::AIO::min_parallel $nthreads
273		325
274	Set the minimum number of AIO threads to C<$nthreads>. The default is	326	Set the minimum number of AIO threads to C<$nthreads>. The current default
275	C<1>, which means a single asynchronous operation can be done at one time	327	is C<4>, which means four asynchronous operations can be done at one time
276	(the number of outstanding operations, however, is unlimited).	328	(the number of outstanding operations, however, is unlimited).
		329
		330	IO::AIO starts threads only on demand, when an AIO request is queued and
		331	no free thread exists.
277		332
278	It is recommended to keep the number of threads low, as some Linux	333	It is recommended to keep the number of threads low, as some Linux
279	kernel versions will scale negatively with the number of threads (higher	334	kernel versions will scale negatively with the number of threads (higher
280	parallelity => MUCH higher latency). With current Linux 2.6 versions, 4-32	335	parallelity => MUCH higher latency). With current Linux 2.6 versions, 4-32
281	threads should be fine.	336	threads should be fine.
282		337
283	Under normal circumstances you don't need to call this function, as this	338	Under most circumstances you don't need to call this function, as the
284	module automatically starts some threads (the exact number might change,	339	module selects a default that is suitable for low to moderate load.
285	and is currently 4).
286		340
287	=item IO::AIO::max_parallel $nthreads	341	=item IO::AIO::max_parallel $nthreads
288		342
289	Sets the maximum number of AIO threads to C<$nthreads>. If more than	343	Sets the maximum number of AIO threads to C<$nthreads>. If more than the
290	the specified number of threads are currently running, kill them. This	344	specified number of threads are currently running, this function kills
291	function blocks until the limit is reached.	345	them. This function blocks until the limit is reached.
		346
		347	While C<$nthreads> are zero, aio requests get queued but not executed
		348	until the number of threads has been increased again.
292		349
293	This module automatically runs C<max_parallel 0> at program end, to ensure	350	This module automatically runs C<max_parallel 0> at program end, to ensure
294	that all threads are killed and that there are no outstanding requests.	351	that all threads are killed and that there are no outstanding requests.
295		352
296	Under normal circumstances you don't need to call this function.	353	Under normal circumstances you don't need to call this function.
…		…
300	Sets the maximum number of outstanding requests to C<$nreqs>. If you	357	Sets the maximum number of outstanding requests to C<$nreqs>. If you
301	try to queue up more than this number of requests, the caller will block until	358	try to queue up more than this number of requests, the caller will block until
302	some requests have been handled.	359	some requests have been handled.
303		360
304	The default is very large, so normally there is no practical limit. If you	361	The default is very large, so normally there is no practical limit. If you
305	queue up many requests in a loop it it often improves speed if you set	362	queue up many requests in a loop it often improves speed if you set
306	this to a relatively low number, such as C<100>.	363	this to a relatively low number, such as C<100>.
307		364
308	Under normal circumstances you don't need to call this function.	365	Under normal circumstances you don't need to call this function.
309		366
310	=back	367	=back
…		…
317		374
318	# try to generate nice filehandles	375	# try to generate nice filehandles
319	my $sym = "IO::AIO::fd#$_[0]";	376	my $sym = "IO::AIO::fd#$_[0]";
320	local *$sym;	377	local *$sym;
321		378
322	open *$sym, "+<&$_[0]" # usually under any unix	379	open *$sym, "+<&=$_[0]" # usually works under any unix
323	or open *$sym, "<&$_[0]" # cygwin needs this	380	or open *$sym, "<&=$_[0]" # cygwin needs this
324	or open *$sym, ">&$_[0]" # cygwin needs this	381	or open *$sym, ">&=$_[0]" # or this
325	or return undef;	382	or return undef;
326		383
327	*$sym	384	*$sym
328	}	385	}
329		386
…		…
333	max_parallel 0;	390	max_parallel 0;
334	}	391	}
335		392
336	1;	393	1;
337		394
		395	=head2 FORK BEHAVIOUR
		396
		397	Before the fork, IO::AIO enters a quiescent state where no requests
		398	can be added in other threads and no results will be processed. After
		399	the fork the parent simply leaves the quiescent state and continues
		400	request/result processing, while the child clears the request/result
		401	queue (so the requests started before the fork will only be handled in
		402	the parent). Threats will be started on demand until the limit ste in the
		403	parent process has been reached again.
		404
338	=head1 SEE ALSO	405	=head1 SEE ALSO
339		406
340	L<Coro>, L<Linux::AIO>.	407	L<Coro>, L<Linux::AIO>.
341		408
342	=head1 AUTHOR	409	=head1 AUTHOR

Diff Legend

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

Comparing IO-AIO/AIO.pm (file contents): Revision 1.25 by root, Sun Jul 31 21:21:12 2005 UTC vs. Revision 1.39 by root, Sun Aug 28 11:05:50 2005 UTC

Diff Legend

Comparing IO-AIO/AIO.pm (file contents):
Revision 1.25 by root, Sun Jul 31 21:21:12 2005 UTC vs.
Revision 1.39 by root, Sun Aug 28 11:05:50 2005 UTC