1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
|
Description: spelling fixes
Origin: vendor
Forwarded: no
Author: gregor herrmann <gregoa@debian.org>
Last-Update: 2016-10-30
--- a/AIO.pm
+++ b/AIO.pm
@@ -118,7 +118,7 @@
The perl object is a fairly standard ref-to-hash object. The hash contents
are not used by IO::AIO so you are free to store anything you like in it.
-During their existance, aio requests travel through the following states,
+During their existence, aio requests travel through the following states,
in order:
=over 4
@@ -292,7 +292,7 @@
which must be a code reference. This code reference will be called after
the syscall has been executed in an asynchronous fashion. The results
of the request will be passed as arguments to the callback (and, if an
-error occured, in C<$!>) - for most requests the syscall return code (e.g.
+error occurred, in C<$!>) - for most requests the syscall return code (e.g.
most syscalls return C<-1> on error, unlike perl, which usually delivers
"false").
@@ -495,7 +495,7 @@
into a trap where C<aio_sendfile> reads some data with readahead, then
fails to write all data, and when the socket is ready the next time, the
data in the cache is already lost, forcing C<aio_sendfile> to again hit
-the disk. Explicit C<aio_read> + C<aio_write> let's you better control
+the disk. Explicit C<aio_read> + C<aio_write> lets you better control
resource usage.
This call tries to make use of a native C<sendfile>-like syscall to
@@ -1573,7 +1573,7 @@
=item aio_wd $pathname, $callback->($wd)
-Asynchonously canonicalise the given pathname and convert it to an
+Asynchronously canonicalise the given pathname and convert it to an
IO::AIO::WD object representing it. If possible and supported on the
system, also open a directory fd to speed up pathname resolution relative
to this working directory.
@@ -1859,7 +1859,7 @@
These set the maximum number of requests (default C<0>, meaning infinity)
that are being processed by C<IO::AIO::poll_cb> in one call, respectively
the maximum amount of time (default C<0>, meaning infinity) spent in
-C<IO::AIO::poll_cb> to process requests (more correctly the mininum amount
+C<IO::AIO::poll_cb> to process requests (more correctly the minimum amount
of time C<poll_cb> is allowed to use).
Setting C<max_poll_time> to a non-zero value creates an overhead of one
@@ -1974,7 +1974,7 @@
IO::AIO::flush;
The call to C<poll_cb> inside the loop will normally return instantly, but
-as soon as more thna C<32> reqeusts are in-flight, it will block until
+as soon as more thna C<32> requests are in-flight, it will block until
some requests have been handled. This keeps the loop from pushing a large
number of C<aio_stat> requests onto the queue.
|
