1
0
mirror of https://git.FreeBSD.org/ports.git synced 2024-12-12 03:00:28 +00:00

Update to 4.7

- Update COMMENT
- Update pkg-descr
- Take maintainership

Changes:	https://metacpan.org/changes/distribution/IO-AIO
This commit is contained in:
Sunpoet Po-Chuan Hsieh 2019-04-21 19:06:44 +00:00
parent 2812d60524
commit 0b15de002d
Notes: svn2git 2021-03-31 03:12:20 +00:00
svn path=/head/; revision=499559
3 changed files with 25 additions and 24 deletions

View File

@ -2,14 +2,13 @@
# $FreeBSD$
PORTNAME= IO-AIO
PORTVERSION= 4.70
PORTVERSION= 4.72
CATEGORIES= devel perl5
MASTER_SITES= CPAN
PKGNAMEPREFIX= p5-
DISTNAME= ${PORTNAME}-${PORTVERSION:S|0$||}
MAINTAINER= perl@FreeBSD.org
COMMENT= Asynchronous Input/Output
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Asynchronous/Advanced Input/Output
LICENSE= ART10 GPLv1+
LICENSE_COMB= dual

View File

@ -1,3 +1,3 @@
TIMESTAMP = 1551888566
SHA256 (IO-AIO-4.7.tar.gz) = 31501b7307d2b1646b2b6412b10065b028a0245534a6b14ed5c2399c160ea01c
SIZE (IO-AIO-4.7.tar.gz) = 172613
TIMESTAMP = 1555856834
SHA256 (IO-AIO-4.72.tar.gz) = 6e5b5e82c95f36d4e26d0745e1bddef0f0beb313b7dae296a668a9fb145e6e9f
SIZE (IO-AIO-4.72.tar.gz) = 176906

View File

@ -1,21 +1,23 @@
This module implements asynchronous I/O using whatever means your
operating system supports.
IO::AIO implements asynchronous I/O using whatever means your operating system
supports. It is implemented as an interface to libeio.
Asynchronous means that operations that can normally block your
program (e.g. reading from disk) will be done asynchronously: the
operation will still block, but you can do something else in the
meantime. This is extremely useful for programs that need to stay
interactive even when doing heavy I/O (GUI programs, high performance
network servers etc.), but can also be used to easily do operations in
parallel that are normally done sequentially, e.g. stat'ing many files,
which is much faster on a RAID volume or over NFS when you do a number
of stat operations concurrently.
Asynchronous means that operations that can normally block your program (e.g.
reading from disk) will be done asynchronously: the operation will still block,
but you can do something else in the meantime. This is extremely useful for
programs that need to stay interactive even when doing heavy I/O (GUI programs,
high performance network servers etc.), but can also be used to easily do
operations in parallel that are normally done sequentially, e.g. stat'ing many
files, which is much faster on a RAID volume or over NFS when you do a number of
stat operations concurrently.
While most of this works on all types of file descriptors (for example
sockets), using these functions on file descriptors that support
nonblocking operation (again, sockets, pipes etc.) is very inefficient
or might not work (aio_read fails on sockets/pipes/fifos). Use an
event loop for that (such as the Event module): IO::AIO will naturally
fit into such an event loop itself.
While most of this works on all types of file descriptors (for example sockets),
using these functions on file descriptors that support nonblocking operation
(again, sockets, pipes etc.) is very inefficient. Use an event loop for that
(such as the EV module): IO::AIO will naturally fit into such an event loop
itself.
In addition to asynchronous I/O, this module also exports some rather arcane
interfaces, such as madvise or linux's splice system call, which is why the A in
AIO can also mean advanced.
WWW: https://metacpan.org/release/IO-AIO