Berkeley DB: memp_fopen
Полезная информация


#include <db.h>

int memp_fopen(DB_MPOOL *mp, char *file, u_int32_t flags, int mode, size_t pagesize, DB_MPOOL_FINFO *finfop, DB_MPOOLFILE **mpf);


The memp_fopen function opens a file in the pool specified by the DB_MPOOL mp, copying the DB_MPOOLFILE pointer representing it into the memory location referenced by mpf.

The file argument is the name of the file to be opened. If file is NULL, a private file is created that cannot be shared with any other process (although it may be shared with other threads).

The flags and mode arguments specify how files will be opened and/or created if they do not already exist. The flags value is specified by logically OR'ing together one or more of the following values:

Create any underlying files, as necessary. If the files do not already exist and the DB_CREATE flag is not specified, the call will fail.

Always copy this file into the local cache instead of mapping it into process memory (see the description of the mp_mmapsize field of the DB_ENV structure for further information).

Open any underlying files for reading only. Any attempt to write the file using the pool functions will fail, regardless of the actual permissions of the file.

All files created by the function memp_fopen are created with mode mode (as described in chmod(2)) and modified by the process' umask value at the time of creation (see umask(2)))). The group ownership of created files is based on the system and directory defaults, and is not further specified by Berkeley DB.

The pagesize argument is the size, in bytes, of the unit of transfer between the application and the pool, although it is not necessarily the unit of transfer between the pool and the source file.

Files opened in the pool may be further configured based on the finfop argument to memp_fopen, which is a pointer to a structure of type DB_MPOOL_FINFO). No references to the finfop structure are maintained by Berkeley DB, so it may be discarded when the memp_fopen function returns. In order to ensure compatibility with future releases of Berkeley DB, all fields of the DB_MPOOL_FINFO structure that are not explicitly set should be initialized to 0 before the first time the structure is used. Do this by declaring the structure external or static, or by calling the C library routine bzero(3) or memset(3).

The fields of the DB_MPOOL_FINFO structure used by memp_fopen are described below. If finfop is NULL or any of its fields are set to their default value, defaults appropriate for the system are used.

int ftype;
The ftype field should be the same as a ftype argument previously specified to the memp_register function, unless no input or output processing of the file's pages are necessary, in which case it should be 0. (See the description of the memp_register function for more information.)

DBT *pgcookie;
The pgcookie field contains the byte string that is passed to the pgin and pgout functions for this file, if any. If no pgin or pgout functions are specified, the pgcookie field should be NULL. (See the description of the memp_register function for more information.)

u_int8_t *fileid;
The fileid field is a unique identifier for the file. The mpool functions must be able to uniquely identify files in order that multiple processes sharing a file will correctly share its underlying pages. Normally, the fileid field should be NULL and the mpool functions will use the file's device and inode numbers (see stat(2))) for this purpose. On some filesystems, (e.g., FAT or NFS) file device and inode numbers are not necessarily unique across system reboots.

Applications wanting to maintain a shared memory buffer pool across system reboots, where the pool contains pages from files stored on such filesystems, must specify a unique file identifier to the memp_fopen call and each process opening or registering the file must provide the same unique identifier.

If the fileid field is non-NULL, it must reference a DB_FILE_ID_LEN length array of bytes that will be used to uniquely identify the file. This should not be necessary for most applications. Specifically, it is not necessary if the memory pool is re-instantiated after each system reboot, the application is using the Berkeley DB access methods instead of calling the pool functions explicitly, or the files in the memory pool are stored on filesystems where the file device and inode numbers do not change across system reboots.

int32_t lsn_offset;
The lsn_offset field is the zero-based byte offset in the page of the page's log sequence number (LSN), or -1 if no LSN offset is specified. (See the description of the memp_sync function for more information.)

u_int32_t clear_len;
The clear_len field is the number of initial bytes in a page that should be set to zero when the page is created as a result of the DB_MPOOL_CREATE or DB_MPOOL_NEW flags being specified to memp_fget. If finfop is NULL or clear_len is 0, the entire page is cleared.

The memp_fopen function returns the value of errno on failure, and 0 on success.


If a fatal error occurs in Berkeley DB, the memp_fopen function may fail and return DB_RUNRECOVERY, at which point all subsequent database calls will also return DB_RUNRECOVERY.

The memp_fopen function may fail and return errno for any of the errors specified for the following Berkeley DB and C library functions: DBmemp->pgin(3), DBmemp->pgout(3), abort(3), close(3), dbenv->db_paniccall(3), fcntl(3), fflush(3), fprintf(3), free(3), fstat(3), fsync(3), getenv(3), getpid(3), getuid(3), isdigit(3), log_compare, log_flush, lseek(3), malloc(3), memcmp(3), memcpy(3), memset(3), mmap(3), open(3), pread(3), pstat_getdynamic(3), pwrite(3), read(3), sigfillset(3), sigprocmask(3), stat(3), strerror(3), strlen(3), sysconf(3), time(3), unlink(3), vfprintf(3), vsnprintf(3), and write(3).

In addition, the memp_fopen function may fail and return errno for the following conditions:

An invalid flag value or parameter was specified.

The file has already been entered into the pool, and the pagesize value is not the same as when the file was entered into the pool, or the length of the file is not zero or a multiple of the pagesize.

The DB_RDONLY flag was specified for an in-memory pool.

See Also

memp_close, memp_fclose, memp_fget, memp_fopen, memp_fput, memp_fset, memp_fsync, memp_open, memp_register, memp_stat, memp_stat, memp_sync, memp_trickle and memp_unlink.