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

Comparing IO-AIO/AIO.pm (file contents):
Revision 1.283 by root, Tue Feb 20 06:05:19 2018 UTC vs.
Revision 1.287 by root, Tue Jul 24 04:58:59 2018 UTC

 use common::sense;
 use base 'Exporter';
 BEGIN {
-   our $VERSION = 4.4;
+   our $VERSION = 4.42;
    our @AIO_REQ = qw(aio_sendfile aio_seek aio_read aio_write aio_open aio_close
                      aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx
                      aio_scandir aio_symlink aio_readlink aio_realpath aio_fcntl aio_ioctl
                      aio_sync aio_fsync aio_syncfs aio_fdatasync aio_sync_file_range
    our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush
                        min_parallel max_parallel max_idle idle_timeout
                        nreqs nready npending nthreads
                        max_poll_time max_poll_reqs
                        sendfile fadvise madvise
-                       mmap munmap munlock munlockall);
+                       mmap munmap mremap munlock munlockall);
    push @AIO_REQ, qw(aio_busy); # not exported
    @IO::AIO::GRP::ISA = 'IO::AIO::REQ';
    IO::AIO::sendfile $ofh, $ifh, $offset, $count
    IO::AIO::fadvise $fh, $offset, $len, $advice
    IO::AIO::mmap $scalar, $length, $prot, $flags[, $fh[, $offset]]
    IO::AIO::munmap $scalar
+   IO::AIO::mremap $scalar, $new_length, $flags[, $new_address]
    IO::AIO::madvise $scalar, $offset, $length, $advice
    IO::AIO::mprotect $scalar, $offset, $length, $protect
    IO::AIO::munlock $scalar, $offset = 0, $length = undef
    IO::AIO::munlockall
 following POSIX and non-POSIX constants are available (missing ones on
 your system are, as usual, C<0>):
 C<O_ASYNC>, C<O_DIRECT>, C<O_NOATIME>, C<O_CLOEXEC>, C<O_NOCTTY>, C<O_NOFOLLOW>,
 C<O_NONBLOCK>, C<O_EXEC>, C<O_SEARCH>, C<O_DIRECTORY>, C<O_DSYNC>,
-C<O_RSYNC>, C<O_SYNC>, C<O_PATH>, C<O_TMPFILE>, and C<O_TTY_INIT>.
+C<O_RSYNC>, C<O_SYNC>, C<O_PATH>, C<O_TMPFILE>, C<O_TTY_INIT> and C<O_ACCMODE>.
 =item aio_close $fh, $callback->($status)
 Asynchronously close a file and call the callback with the result
 =over 4
 =item IO::AIO::READDIR_DENTS
-When this flag is off, then the callback gets an arrayref consisting of
+Normally the callback gets an arrayref consisting of names only (as
-names only (as with C<aio_readdir>), otherwise it gets an arrayref with
+with C<aio_readdir>). If this flag is set, then the callback gets an
-C<[$name, $type, $inode]> arrayrefs, each describing a single directory
+arrayref with C<[$name, $type, $inode]> arrayrefs, each describing a
-entry in more detail.
+single directory entry in more detail:
 C<$name> is the name of the entry.
 C<$type> is one of the C<IO::AIO::DT_xxx> constants:
 C<IO::AIO::DT_UNKNOWN>, C<IO::AIO::DT_FIFO>, C<IO::AIO::DT_CHR>, C<IO::AIO::DT_DIR>,
 C<IO::AIO::DT_BLK>, C<IO::AIO::DT_REG>, C<IO::AIO::DT_LNK>, C<IO::AIO::DT_SOCK>,
 C<IO::AIO::DT_WHT>.
-C<IO::AIO::DT_UNKNOWN> means just that: readdir does not know. If you need to
+C<IO::AIO::DT_UNKNOWN> means just that: readdir does not know. If you need
-know, you have to run stat yourself. Also, for speed reasons, the C<$type>
+to know, you have to run stat yourself. Also, for speed/memory reasons,
-scalars are read-only: you can not modify them.
+the C<$type> scalars are read-only: you must not modify them.
 C<$inode> is the inode number (which might not be exact on systems with 64
 bit inode numbers and 32 bit perls). This field has unspecified content on
 systems that do not deliver the inode information.
 short names are tried first.
 =item IO::AIO::READDIR_STAT_ORDER
 When this flag is set, then the names will be returned in an order
-suitable for stat()'ing each one. That is, when you plan to stat()
+suitable for stat()'ing each one. That is, when you plan to stat() most or
-all files in the given directory, then the returned order will likely
+all files in the given directory, then the returned order will likely be
-be fastest.
+faster.
-If both this flag and C<IO::AIO::READDIR_DIRS_FIRST> are specified, then
+If both this flag and C<IO::AIO::READDIR_DIRS_FIRST> are specified,
-the likely dirs come first, resulting in a less optimal stat order.
+then the likely dirs come first, resulting in a less optimal stat order
+for stat'ing all entries, but likely a more optimal order for finding
+subdirectories.
 =item IO::AIO::READDIR_FOUND_UNKNOWN
 This flag should not be set when calling C<aio_readdirx>. Instead, it
 is being set by C<aio_readdirx>, when any of the C<$type>'s found were
 =item IO::AIO::munmap $scalar
 Removes a previous mmap and undefines the C<$scalar>.
+=item IO::AIO::mremap $scalar, $new_length, $flags = MREMAP_MAYMOVE[, $new_address = 0]
+Calls the Linux-specific mremap(2) system call. The C<$scalar> must have
+been mapped by C<IO::AIO::mmap>, and C<$flags> must currently either be
+C<0> or C<IO::AIO::MREMAP_MAYMOVE>.
+Returns true if successful, and false otherwise. If the underlying mmapped
+region has changed address, then the true value has the numerical value
+C<1>, otherwise it has the numerical value C<0>:
+   my $success = IO::AIO::mremap $mmapped, 8192, IO::AIO::MREMAP_MAYMOVE
+      or die "mremap: $!";
+   if ($success*1) {
+      warn "scalar has chanegd address in memory\n";
+   }
+C<IO::AIO::MREMAP_FIXED> and the C<$new_address> argument are currently
+implemented, but not supported and might go away in a future version.
+On systems where this call is not supported or is not emulated, this call
+returns falls and sets C<$!> to C<ENOSYS>.
 =item IO::AIO::munlock $scalar, $offset = 0, $length = undef
 Calls the C<munlock> function, undoing the effects of a previous
 C<aio_mlock> call (see its description for details).

Diff Legend

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

Comparing IO-AIO/AIO.pm (file contents): Revision 1.283 by root, Tue Feb 20 06:05:19 2018 UTC vs. Revision 1.287 by root, Tue Jul 24 04:58:59 2018 UTC

Diff Legend

Comparing IO-AIO/AIO.pm (file contents):
Revision 1.283 by root, Tue Feb 20 06:05:19 2018 UTC vs.
Revision 1.287 by root, Tue Jul 24 04:58:59 2018 UTC