… | |
… | |
168 | use common::sense; |
168 | use common::sense; |
169 | |
169 | |
170 | use base 'Exporter'; |
170 | use base 'Exporter'; |
171 | |
171 | |
172 | BEGIN { |
172 | BEGIN { |
173 | our $VERSION = '3.65'; |
173 | our $VERSION = '3.9'; |
174 | |
174 | |
175 | our @AIO_REQ = qw(aio_sendfile aio_read aio_write aio_open aio_close |
175 | our @AIO_REQ = qw(aio_sendfile aio_read aio_write aio_open aio_close |
176 | aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx |
176 | aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx |
177 | aio_scandir aio_symlink aio_readlink aio_sync aio_fsync |
177 | aio_scandir aio_symlink aio_readlink aio_sync aio_fsync |
178 | aio_fdatasync aio_sync_file_range aio_pathsync aio_readahead |
178 | aio_fdatasync aio_sync_file_range aio_pathsync aio_readahead |
… | |
… | |
182 | aio_msync aio_mtouch aio_mlock aio_mlockall |
182 | aio_msync aio_mtouch aio_mlock aio_mlockall |
183 | aio_statvfs); |
183 | aio_statvfs); |
184 | |
184 | |
185 | our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice)); |
185 | our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice)); |
186 | our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush |
186 | our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush |
187 | min_parallel max_parallel max_idle |
187 | min_parallel max_parallel max_idle idle_timeout |
188 | nreqs nready npending nthreads |
188 | nreqs nready npending nthreads |
189 | max_poll_time max_poll_reqs |
189 | max_poll_time max_poll_reqs |
190 | sendfile fadvise madvise |
190 | sendfile fadvise madvise |
191 | mmap munmap munlock munlockall); |
191 | mmap munmap munlock munlockall); |
192 | |
192 | |
… | |
… | |
258 | IO::AIO::max_poll_reqs $nreqs |
258 | IO::AIO::max_poll_reqs $nreqs |
259 | IO::AIO::max_poll_time $seconds |
259 | IO::AIO::max_poll_time $seconds |
260 | IO::AIO::min_parallel $nthreads |
260 | IO::AIO::min_parallel $nthreads |
261 | IO::AIO::max_parallel $nthreads |
261 | IO::AIO::max_parallel $nthreads |
262 | IO::AIO::max_idle $nthreads |
262 | IO::AIO::max_idle $nthreads |
|
|
263 | IO::AIO::idle_timeout $seconds |
263 | IO::AIO::max_outstanding $maxreqs |
264 | IO::AIO::max_outstanding $maxreqs |
264 | IO::AIO::nreqs |
265 | IO::AIO::nreqs |
265 | IO::AIO::nready |
266 | IO::AIO::nready |
266 | IO::AIO::npending |
267 | IO::AIO::npending |
267 | |
268 | |
268 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
269 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
269 | IO::AIO::fadvise $fh, $offset, $len, $advice |
270 | IO::AIO::fadvise $fh, $offset, $len, $advice |
|
|
271 | IO::AIO::madvise $scalar, $offset, $length, $advice |
|
|
272 | IO::AIO::mprotect $scalar, $offset, $length, $protect |
270 | IO::AIO::munlock $scalar, $offset = 0, $length = undef |
273 | IO::AIO::munlock $scalar, $offset = 0, $length = undef |
271 | IO::AIO::munlockall |
274 | IO::AIO::munlockall |
272 | |
275 | |
273 | =head2 AIO REQUEST FUNCTIONS |
276 | =head2 AIO REQUEST FUNCTIONS |
274 | |
277 | |
… | |
… | |
365 | } else { |
368 | } else { |
366 | die "open failed: $!\n"; |
369 | die "open failed: $!\n"; |
367 | } |
370 | } |
368 | }; |
371 | }; |
369 | |
372 | |
|
|
373 | In addition to all the common open modes/flags (C<O_RDONLY>, C<O_WRONLY>, |
|
|
374 | C<O_RDWR>, C<O_CREAT>, C<O_TRUNC>, C<O_EXCL> and C<O_APPEND>), the |
|
|
375 | following POSIX and non-POSIX constants are available (missing ones on |
|
|
376 | your system are, as usual, C<0>): |
|
|
377 | |
|
|
378 | C<O_ASYNC>, C<O_DIRECT>, C<O_NOATIME>, C<O_CLOEXEC>, C<O_NOCTTY>, C<O_NOFOLLOW>, |
|
|
379 | C<O_NONBLOCK>, C<O_EXEC>, C<O_SEARCH>, C<O_DIRECTORY>, C<O_DSYNC>, |
|
|
380 | C<O_RSYNC>, C<O_SYNC> and C<O_TTY_INIT>. |
|
|
381 | |
370 | |
382 | |
371 | =item aio_close $fh, $callback->($status) |
383 | =item aio_close $fh, $callback->($status) |
372 | |
384 | |
373 | Asynchronously close a file and call the callback with the result |
385 | Asynchronously close a file and call the callback with the result |
374 | code. |
386 | code. |
… | |
… | |
426 | reading at byte offset C<$in_offset>, and starts writing at the current |
438 | reading at byte offset C<$in_offset>, and starts writing at the current |
427 | file offset of C<$out_fh>. Because of that, it is not safe to issue more |
439 | file offset of C<$out_fh>. Because of that, it is not safe to issue more |
428 | than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each |
440 | than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each |
429 | other. |
441 | other. |
430 | |
442 | |
|
|
443 | Please note that C<aio_sendfile> can read more bytes from C<$in_fh> than |
|
|
444 | are written, and there is no way to find out how many bytes have been read |
|
|
445 | from C<aio_sendfile> alone, as C<aio_sendfile> only provides the number of |
|
|
446 | bytes written to C<$out_fh>. Only if the result value equals C<$length> |
|
|
447 | one can assume that C<$length> bytes have been read. |
|
|
448 | |
|
|
449 | Unlike with other C<aio_> functions, it makes a lot of sense to use |
|
|
450 | C<aio_sendfile> on non-blocking sockets, as long as one end (typically |
|
|
451 | the C<$in_fh>) is a file - the file I/O will then be asynchronous, while |
|
|
452 | the socket I/O will be non-blocking. Note, however, that you can run into |
|
|
453 | a trap where C<aio_sendfile> reads some data with readahead, then fails |
|
|
454 | to write all data, and when the socket is ready the next time, the data |
|
|
455 | in the cache is already lost, forcing C<aio_sendfile> to again hit the |
|
|
456 | disk. Explicit C<aio_read> + C<aio_write> let's you control resource usage |
|
|
457 | much better. |
|
|
458 | |
431 | This call tries to make use of a native C<sendfile> syscall to provide |
459 | This call tries to make use of a native C<sendfile> syscall to provide |
432 | zero-copy operation. For this to work, C<$out_fh> should refer to a |
460 | zero-copy operation. For this to work, C<$out_fh> should refer to a |
433 | socket, and C<$in_fh> should refer to an mmap'able file. |
461 | socket, and C<$in_fh> should refer to an mmap'able file. |
434 | |
462 | |
435 | If a native sendfile cannot be found or it fails with C<ENOSYS>, |
463 | If a native sendfile cannot be found or it fails with C<ENOSYS>, |
436 | C<ENOTSUP>, C<EOPNOTSUPP>, C<EAFNOSUPPORT>, C<EPROTOTYPE> or C<ENOTSOCK>, |
464 | C<ENOTSUP>, C<EOPNOTSUPP>, C<EAFNOSUPPORT>, C<EPROTOTYPE> or C<ENOTSOCK>, |
437 | it will be emulated, so you can call C<aio_sendfile> on any type of |
465 | it will be emulated, so you can call C<aio_sendfile> on any type of |
438 | filehandle regardless of the limitations of the operating system. |
466 | filehandle regardless of the limitations of the operating system. |
439 | |
|
|
440 | Please note, however, that C<aio_sendfile> can read more bytes from |
|
|
441 | C<$in_fh> than are written, and there is no way to find out how many |
|
|
442 | bytes have been read from C<aio_sendfile> alone, as C<aio_sendfile> only |
|
|
443 | provides the number of bytes written to C<$out_fh>. Only if the result |
|
|
444 | value equals C<$length> one can assume that C<$length> bytes have been |
|
|
445 | read. |
|
|
446 | |
467 | |
447 | |
468 | |
448 | =item aio_readahead $fh,$offset,$length, $callback->($retval) |
469 | =item aio_readahead $fh,$offset,$length, $callback->($retval) |
449 | |
470 | |
450 | C<aio_readahead> populates the page cache with data from a file so that |
471 | C<aio_readahead> populates the page cache with data from a file so that |
… | |
… | |
472 | for an explanation. |
493 | for an explanation. |
473 | |
494 | |
474 | Currently, the stats are always 64-bit-stats, i.e. instead of returning an |
495 | Currently, the stats are always 64-bit-stats, i.e. instead of returning an |
475 | error when stat'ing a large file, the results will be silently truncated |
496 | error when stat'ing a large file, the results will be silently truncated |
476 | unless perl itself is compiled with large file support. |
497 | unless perl itself is compiled with large file support. |
|
|
498 | |
|
|
499 | To help interpret the mode and dev/rdev stat values, IO::AIO offers the |
|
|
500 | following constants and functions (if not implemented, the constants will |
|
|
501 | be C<0> and the functions will either C<croak> or fall back on traditional |
|
|
502 | behaviour). |
|
|
503 | |
|
|
504 | C<S_IFMT>, C<S_IFIFO>, C<S_IFCHR>, C<S_IFBLK>, C<S_IFLNK>, C<S_IFREG>, |
|
|
505 | C<S_IFDIR>, C<S_IFWHT>, C<S_IFSOCK>, C<IO::AIO::major $dev_t>, |
|
|
506 | C<IO::AIO::minor $dev_t>, C<IO::AIO::makedev $major, $minor>. |
477 | |
507 | |
478 | Example: Print the length of F</etc/passwd>: |
508 | Example: Print the length of F</etc/passwd>: |
479 | |
509 | |
480 | aio_stat "/etc/passwd", sub { |
510 | aio_stat "/etc/passwd", sub { |
481 | $_[0] and die "stat failed: $!"; |
511 | $_[0] and die "stat failed: $!"; |
… | |
… | |
583 | |
613 | |
584 | The only (POSIX-) portable way of calling this function is: |
614 | The only (POSIX-) portable way of calling this function is: |
585 | |
615 | |
586 | aio_mknod $path, IO::AIO::S_IFIFO | $mode, 0, sub { ... |
616 | aio_mknod $path, IO::AIO::S_IFIFO | $mode, 0, sub { ... |
587 | |
617 | |
|
|
618 | See C<aio_stat> for info about some potentially helpful extra constants |
|
|
619 | and functions. |
588 | |
620 | |
589 | =item aio_link $srcpath, $dstpath, $callback->($status) |
621 | =item aio_link $srcpath, $dstpath, $callback->($status) |
590 | |
622 | |
591 | Asynchronously create a new link to the existing object at C<$srcpath> at |
623 | Asynchronously create a new link to the existing object at C<$srcpath> at |
592 | the path C<$dstpath> and call the callback with the result code. |
624 | the path C<$dstpath> and call the callback with the result code. |
… | |
… | |
645 | |
677 | |
646 | =over 4 |
678 | =over 4 |
647 | |
679 | |
648 | =item IO::AIO::READDIR_DENTS |
680 | =item IO::AIO::READDIR_DENTS |
649 | |
681 | |
650 | When this flag is off, then the callback gets an arrayref with of names |
682 | When this flag is off, then the callback gets an arrayref consisting of |
651 | only (as with C<aio_readdir>), otherwise it gets an arrayref with |
683 | names only (as with C<aio_readdir>), otherwise it gets an arrayref with |
652 | C<[$name, $type, $inode]> arrayrefs, each describing a single directory |
684 | C<[$name, $type, $inode]> arrayrefs, each describing a single directory |
653 | entry in more detail. |
685 | entry in more detail. |
654 | |
686 | |
655 | C<$name> is the name of the entry. |
687 | C<$name> is the name of the entry. |
656 | |
688 | |
… | |
… | |
669 | systems that do not deliver the inode information. |
701 | systems that do not deliver the inode information. |
670 | |
702 | |
671 | =item IO::AIO::READDIR_DIRS_FIRST |
703 | =item IO::AIO::READDIR_DIRS_FIRST |
672 | |
704 | |
673 | When this flag is set, then the names will be returned in an order where |
705 | When this flag is set, then the names will be returned in an order where |
674 | likely directories come first. This is useful when you need to quickly |
706 | likely directories come first, in optimal stat order. This is useful when |
675 | find directories, or you want to find all directories while avoiding to |
707 | you need to quickly find directories, or you want to find all directories |
676 | stat() each entry. |
708 | while avoiding to stat() each entry. |
677 | |
709 | |
678 | If the system returns type information in readdir, then this is used |
710 | If the system returns type information in readdir, then this is used |
679 | to find directories directly. Otherwise, likely directories are files |
711 | to find directories directly. Otherwise, likely directories are names |
680 | beginning with ".", or otherwise files with no dots, of which files with |
712 | beginning with ".", or otherwise names with no dots, of which names with |
681 | short names are tried first. |
713 | short names are tried first. |
682 | |
714 | |
683 | =item IO::AIO::READDIR_STAT_ORDER |
715 | =item IO::AIO::READDIR_STAT_ORDER |
684 | |
716 | |
685 | When this flag is set, then the names will be returned in an order |
717 | When this flag is set, then the names will be returned in an order |
… | |
… | |
1383 | |
1415 | |
1384 | See C<poll_cb> for an example. |
1416 | See C<poll_cb> for an example. |
1385 | |
1417 | |
1386 | =item IO::AIO::poll_cb |
1418 | =item IO::AIO::poll_cb |
1387 | |
1419 | |
1388 | Process some outstanding events on the result pipe. You have to call this |
1420 | Process some outstanding events on the result pipe. You have to call |
1389 | regularly. Returns C<0> if all events could be processed, or C<-1> if it |
1421 | this regularly. Returns C<0> if all events could be processed (or there |
1390 | returned earlier for whatever reason. Returns immediately when no events |
1422 | were no events to process), or C<-1> if it returned earlier for whatever |
1391 | are outstanding. The amount of events processed depends on the settings of |
1423 | reason. Returns immediately when no events are outstanding. The amount of |
1392 | C<IO::AIO::max_poll_req> and C<IO::AIO::max_poll_time>. |
1424 | events processed depends on the settings of C<IO::AIO::max_poll_req> and |
|
|
1425 | C<IO::AIO::max_poll_time>. |
1393 | |
1426 | |
1394 | If not all requests were processed for whatever reason, the filehandle |
1427 | If not all requests were processed for whatever reason, the filehandle |
1395 | will still be ready when C<poll_cb> returns, so normally you don't have to |
1428 | will still be ready when C<poll_cb> returns, so normally you don't have to |
1396 | do anything special to have it called later. |
1429 | do anything special to have it called later. |
|
|
1430 | |
|
|
1431 | Apart from calling C<IO::AIO::poll_cb> when the event filehandle becomes |
|
|
1432 | ready, it can be beneficial to call this function from loops which submit |
|
|
1433 | a lot of requests, to make sure the results get processed when they become |
|
|
1434 | available and not just when the loop is finished and the event loop takes |
|
|
1435 | over again. This function returns very fast when there are no outstanding |
|
|
1436 | requests. |
1397 | |
1437 | |
1398 | Example: Install an Event watcher that automatically calls |
1438 | Example: Install an Event watcher that automatically calls |
1399 | IO::AIO::poll_cb with high priority (more examples can be found in the |
1439 | IO::AIO::poll_cb with high priority (more examples can be found in the |
1400 | SYNOPSIS section, at the top of this document): |
1440 | SYNOPSIS section, at the top of this document): |
1401 | |
1441 | |
… | |
… | |
1503 | |
1543 | |
1504 | Under normal circumstances you don't need to call this function. |
1544 | Under normal circumstances you don't need to call this function. |
1505 | |
1545 | |
1506 | =item IO::AIO::max_idle $nthreads |
1546 | =item IO::AIO::max_idle $nthreads |
1507 | |
1547 | |
1508 | Limit the number of threads (default: 4) that are allowed to idle (i.e., |
1548 | Limit the number of threads (default: 4) that are allowed to idle |
1509 | threads that did not get a request to process within 10 seconds). That |
1549 | (i.e., threads that did not get a request to process within the idle |
1510 | means if a thread becomes idle while C<$nthreads> other threads are also |
1550 | timeout (default: 10 seconds). That means if a thread becomes idle while |
1511 | idle, it will free its resources and exit. |
1551 | C<$nthreads> other threads are also idle, it will free its resources and |
|
|
1552 | exit. |
1512 | |
1553 | |
1513 | This is useful when you allow a large number of threads (e.g. 100 or 1000) |
1554 | This is useful when you allow a large number of threads (e.g. 100 or 1000) |
1514 | to allow for extremely high load situations, but want to free resources |
1555 | to allow for extremely high load situations, but want to free resources |
1515 | under normal circumstances (1000 threads can easily consume 30MB of RAM). |
1556 | under normal circumstances (1000 threads can easily consume 30MB of RAM). |
1516 | |
1557 | |
1517 | The default is probably ok in most situations, especially if thread |
1558 | The default is probably ok in most situations, especially if thread |
1518 | creation is fast. If thread creation is very slow on your system you might |
1559 | creation is fast. If thread creation is very slow on your system you might |
1519 | want to use larger values. |
1560 | want to use larger values. |
1520 | |
1561 | |
|
|
1562 | =item IO::AIO::idle_timeout $seconds |
|
|
1563 | |
|
|
1564 | Sets the minimum idle timeout (default 10) after which worker threads are |
|
|
1565 | allowed to exit. SEe C<IO::AIO::max_idle>. |
|
|
1566 | |
1521 | =item IO::AIO::max_outstanding $maxreqs |
1567 | =item IO::AIO::max_outstanding $maxreqs |
|
|
1568 | |
|
|
1569 | Sets the maximum number of outstanding requests to C<$nreqs>. If |
|
|
1570 | you do queue up more than this number of requests, the next call to |
|
|
1571 | C<IO::AIO::poll_cb> (and other functions calling C<poll_cb>, such as |
|
|
1572 | C<IO::AIO::flush> or C<IO::AIO::poll>) will block until the limit is no |
|
|
1573 | longer exceeded. |
|
|
1574 | |
|
|
1575 | In other words, this setting does not enforce a queue limit, but can be |
|
|
1576 | used to make poll functions block if the limit is exceeded. |
1522 | |
1577 | |
1523 | This is a very bad function to use in interactive programs because it |
1578 | This is a very bad function to use in interactive programs because it |
1524 | blocks, and a bad way to reduce concurrency because it is inexact: Better |
1579 | blocks, and a bad way to reduce concurrency because it is inexact: Better |
1525 | use an C<aio_group> together with a feed callback. |
1580 | use an C<aio_group> together with a feed callback. |
1526 | |
1581 | |
1527 | Sets the maximum number of outstanding requests to C<$nreqs>. If you |
1582 | It's main use is in scripts without an event loop - when you want to stat |
1528 | do queue up more than this number of requests, the next call to the |
1583 | a lot of files, you can write somehting like this: |
1529 | C<poll_cb> (and C<poll_some> and other functions calling C<poll_cb>) |
|
|
1530 | function will block until the limit is no longer exceeded. |
|
|
1531 | |
1584 | |
1532 | The default value is very large, so there is no practical limit on the |
1585 | IO::AIO::max_outstanding 32; |
1533 | number of outstanding requests. |
|
|
1534 | |
1586 | |
1535 | You can still queue as many requests as you want. Therefore, |
1587 | for my $path (...) { |
1536 | C<max_outstanding> is mainly useful in simple scripts (with low values) or |
1588 | aio_stat $path , ...; |
1537 | as a stop gap to shield against fatal memory overflow (with large values). |
1589 | IO::AIO::poll_cb; |
|
|
1590 | } |
|
|
1591 | |
|
|
1592 | IO::AIO::flush; |
|
|
1593 | |
|
|
1594 | The call to C<poll_cb> inside the loop will normally return instantly, but |
|
|
1595 | as soon as more thna C<32> reqeusts are in-flight, it will block until |
|
|
1596 | some requests have been handled. This keeps the loop from pushing a large |
|
|
1597 | number of C<aio_stat> requests onto the queue. |
|
|
1598 | |
|
|
1599 | The default value for C<max_outstanding> is very large, so there is no |
|
|
1600 | practical limit on the number of outstanding requests. |
1538 | |
1601 | |
1539 | =back |
1602 | =back |
1540 | |
1603 | |
1541 | =head3 STATISTICAL INFORMATION |
1604 | =head3 STATISTICAL INFORMATION |
1542 | |
1605 | |
… | |
… | |
1580 | |
1643 | |
1581 | Returns the number of bytes copied, or C<-1> on error. |
1644 | Returns the number of bytes copied, or C<-1> on error. |
1582 | |
1645 | |
1583 | =item IO::AIO::fadvise $fh, $offset, $len, $advice |
1646 | =item IO::AIO::fadvise $fh, $offset, $len, $advice |
1584 | |
1647 | |
1585 | Simply calls the C<posix_fadvise> function (see it's |
1648 | Simply calls the C<posix_fadvise> function (see its |
1586 | manpage for details). The following advice constants are |
1649 | manpage for details). The following advice constants are |
1587 | avaiable: C<IO::AIO::FADV_NORMAL>, C<IO::AIO::FADV_SEQUENTIAL>, |
1650 | avaiable: C<IO::AIO::FADV_NORMAL>, C<IO::AIO::FADV_SEQUENTIAL>, |
1588 | C<IO::AIO::FADV_RANDOM>, C<IO::AIO::FADV_NOREUSE>, |
1651 | C<IO::AIO::FADV_RANDOM>, C<IO::AIO::FADV_NOREUSE>, |
1589 | C<IO::AIO::FADV_WILLNEED>, C<IO::AIO::FADV_DONTNEED>. |
1652 | C<IO::AIO::FADV_WILLNEED>, C<IO::AIO::FADV_DONTNEED>. |
1590 | |
1653 | |
1591 | On systems that do not implement C<posix_fadvise>, this function returns |
1654 | On systems that do not implement C<posix_fadvise>, this function returns |
1592 | ENOSYS, otherwise the return value of C<posix_fadvise>. |
1655 | ENOSYS, otherwise the return value of C<posix_fadvise>. |
|
|
1656 | |
|
|
1657 | =item IO::AIO::madvise $scalar, $offset, $len, $advice |
|
|
1658 | |
|
|
1659 | Simply calls the C<posix_madvise> function (see its |
|
|
1660 | manpage for details). The following advice constants are |
|
|
1661 | avaiable: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, |
|
|
1662 | C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, C<IO::AIO::MADV_DONTNEED>. |
|
|
1663 | |
|
|
1664 | On systems that do not implement C<posix_madvise>, this function returns |
|
|
1665 | ENOSYS, otherwise the return value of C<posix_madvise>. |
|
|
1666 | |
|
|
1667 | =item IO::AIO::mprotect $scalar, $offset, $len, $protect |
|
|
1668 | |
|
|
1669 | Simply calls the C<mprotect> function on the preferably AIO::mmap'ed |
|
|
1670 | $scalar (see its manpage for details). The following protect |
|
|
1671 | constants are avaiable: C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_READ>, |
|
|
1672 | C<IO::AIO::PROT_WRITE>, C<IO::AIO::PROT_EXEC>. |
|
|
1673 | |
|
|
1674 | On systems that do not implement C<mprotect>, this function returns |
|
|
1675 | ENOSYS, otherwise the return value of C<mprotect>. |
1593 | |
1676 | |
1594 | =item IO::AIO::mmap $scalar, $length, $prot, $flags, $fh[, $offset] |
1677 | =item IO::AIO::mmap $scalar, $length, $prot, $flags, $fh[, $offset] |
1595 | |
1678 | |
1596 | Memory-maps a file (or anonymous memory range) and attaches it to the |
1679 | Memory-maps a file (or anonymous memory range) and attaches it to the |
1597 | given C<$scalar>, which will act like a string scalar. |
1680 | given C<$scalar>, which will act like a string scalar. |