希望和广大热爱技术的童鞋一起交流,成长。
分类: LINUX
2011-10-20 16:41:11
sendfile(2) - Linux man page
Name
ssize_t sendfile(int out_fd, int in_fd, off_t * offset ", size_t" " count" );
Description
in_fd should be a file descriptor opened for reading and out_fd should be a descriptor opened for writing.
If offset is not NULL, then it points to a variable holding the file offset from which sendfile() will start reading data from in_fd. When sendfile() returns, this variable will be set to the offset of the byte following the last byte that was read. If offset is not NULL, then sendfile() does not modify the current file offset of in_fd; otherwise the current file offset is adjusted to reflect the number of bytes read from in_fd.
count is the number of bytes to copy between the file descriptors.
Presently (Linux 2.6.9): in_fd, must correspond to a file which supports mmap()-like operations (i.e., it cannot be a socket); and out_fd must refer to a socket.
Applications may wish to fall back to / in the case where sendfile() fails with EINVAL or ENOSYS.
Notes
In Linux 2.4 and earlier, out_fd could refer to a regular file, and sendfile() changed the current offset of that file.
Return Value
Errors
EAGAIN :Non-blocking I/O has been selected using O_NONBLOCK and the write would block.
EBADF :The input file was not opened for reading or the output file was not opened for writing.
EFAULT :Bad address.
EINVAL :Descriptor is not valid or locked, or an mmap()-like operation is not available for in_fd.
EIO :Unspecified error while reading from in_fd.
ENOMEM :Insufficient memory to read from in_fd.
Versions
Other Unix systems implement sendfile() with different semantics and prototypes. It should not be used in portable programs.