Linux下的pread和pwrite(转)

　　当对同一文件句柄（在Windows下）或是文件描述符（在Linux下）进行随机读写操作时，会存在文件指针的定位与读/写俩个步骤，但由于这不是一个原子操作，就可能产生如下问题：进程A对某文件先定位到 f1 处，然后被中断，然后进程B对同一文件定位到 f2 处，然后被中断，进程A再次执行，从文件的当前指针处开始读或是写，于是这便产生了不是期望的结果了。（这里要注意，对同一文件的俩次打开，得到的将是俩个不同的句柄或是描述符，所以不用担心这种情况会出问题）

解决办法：

　　在Linux下，pread函数就好像是专门为上面的问题服务的，它本身就是原子性的操作，定位文件指针与读操作一气呵成，而且读操作并不改变文件指针。

　　下面是pread和pwrite的手册：

NAME

pread, pwrite - read from or write to a file descriptor at a given offset  

SYNOPSIS

#define _XOPEN_SOURCE 500

#include <unistd.h>

ssize_t pread(int fd, void *buf, size_t count, off_t offset);

ssize_t pwrite(int fd, const void *buf, size_t count, off_t offset);  

DESCRIPTION

pread() reads up to count bytes from file descriptor fd at offset offset (from the start of the file) into the buffer starting at buf. The file offset is not changed.

pwrite() writes up to count bytes from the buffer starting at buf to the file descriptor fd at offset offset. The file offset is not changed.

The file referenced by fd must be capable of seeking.  

RETURN VALUE

On success, the number of bytes read or written is returned (zero indicates that nothing was written, in the case of pwrite, or end of file, in the case of pread), or -1 on error, in which caseerrno is set to indicate the error.  

ERRORS

pread can fail and set errno to any error specified for read(2) or lseek(2). pwrite can fail and set errno to any error specified for write(2) or lseek(2).  

CONFORMING TO

Unix98  

NOTES

       The pread() and pwrite() system calls are especially useful in
       multithreaded applications.  They allow multiple threads to perform
       I/O on the same file descriptor without being affected by changes to
       the file offset by other threads.

       On Linux, the underlying system calls were renamed in kernel 2.6:
       pread() became pread64(), and pwrite() became pwrite64().  The system
       call numbers remained the same.  The glibc pread() and pwrite()
       wrapper functions transparently deal with the change.

       On some 32-bit architectures, the calling signature for these system
       calls differ, for the reasons described in syscall(2).

BUGS

       POSIX requires that opening a file with the O_APPEND flag should have
       no affect on the location at which pwrite() writes data.  However, on
       Linux, if a file is opened with O_APPEND, pwrite() appends data to
       the end of the file, regardless of the value of offset.

转载于:https://www.cnblogs.com/brill/p/3226439.html