head 1.2; access; symbols RPM_4_2_1:1.1.1.5 RPM_4_2:1.1.1.5 RPM_4_1_1:1.1.1.5 RPM_4_1:1.1.1.4 RPM_4_0_5:1.1.1.3 RPM_4_0_4:1.1.1.2 RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.52.55; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.08; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.48.57; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.07.59; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.56; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB: lock_vec

lock_vec

 APIRef 

#include <db.h>


int
lock_vec(DB_ENV *env, u_int32_t locker, u_int32_t flags,
    DB_LOCKREQ list[], int nlist, DB_LOCKREQ **elistp);

Description

The lock_vec function atomically obtains and releases one or more locks from the lock table. The lock_vec function is intended to support acquisition or trading of multiple locks under one lock table semaphore, as is needed for lock coupling or in multigranularity locking for lock escalation.

The locker argument specified to lock_vec is an unsigned 32-bit integer quantity. It represents the entity requesting or releasing the locks.

The flags value must be set to 0 or the following value:

DB_LOCK_NOWAIT
If a lock cannot be immediately granted because the requested lock conflicts with an existing lock, return instead of waiting for the lock to become available.

The list array provided to lock_vec is typedef'd as DB_LOCKREQ. A DB_LOCKREQ structure has at least the following fields. In order to ensure compatibility with future releases of Berkeley DB, all fields of the DB_LOCKREQ 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 memset(3).

lockop_t op;
The operation to be performed, which must be set to one of the following values:

DB_LOCK_GET
Get the lock defined by the values of the lock, mode, and obj structure fields, for the specified locker. Upon return from lock_vec, if the lock field is non-NULL, a reference to the acquired lock is stored there. (This reference is invalidated by any call to lock_vec or lock_put that releases the lock.)

DB_LOCK_PUT
The lock to which the lock structure field refers is released. The locker argument, and mode and obj fields are ignored.

DB_LOCK_PUT_ALL
All locks held by the specified locker are released. The lock, mode, and obj structure fields are ignored. Locks acquired in operations performed by the current call to lock_vec which appear before the DB_LOCK_PUT_ALL operation are released; those acquired in operations appearing after the DB_LOCK_PUT_ALL operation are not released.

DB_LOCK_PUT_OBJ
All locks held on the object obj are released. The locker argument and the lock and mode structure fields are ignored. Locks acquired in operations performed by the current call to lock_vec that appear before the DB_LOCK_PUT_OBJ operation are released; those acquired in operations appearing after the DB_LOCK_PUT_OBJ operation are not released.

DB_LOCK lock;
A lock reference.

const lockmode_t mode;
The lock mode, used as an index into the environment's lock conflict matrix. When using the default lock conflict matrix, mode must be set to one of the following values:

DB_LOCK_READ
read (shared)
DB_LOCK_WRITE
write (exclusive)
DB_LOCK_IWRITE
intention to write (shared)
DB_LOCK_IREAD
intention to read (shared)
DB_LOCK_IWR
intention to read and write (shared)

See DB_ENV->set_lk_conflicts and Standard Lock Modes for more information on the lock conflict matrix.

const DBT obj;
An untyped byte string that specifies the object to be locked or released. Applications using the locking subsystem directly while also doing locking via the Berkeley DB access methods must take care not to inadvertently lock objects that happen to be equal to the unique file IDs used to lock files. See Access method locking conventions for more information.

The nlist argument specifies the number of elements in the list array.

If any of the requested locks cannot be acquired, or any of the locks to be released cannot be released, the operations before the failing operation are guaranteed to have completed successfully, and lock_vec returns a non-zero value. In addition, if elistp is not NULL, it is set to point to the DB_LOCKREQ entry that was being processed when the error occurred.

If a lock is requested that cannot be immediately granted, and the flags parameter was set to DB_LOCK_NOWAIT, the lock_vec function may return DB_LOCK_NOTGRANTED. In this case, if non-NULL, elistp identifies the request that was not granted.

Otherwise, the lock_vec function returns a non-zero error value on failure and 0 on success.

Errors

The lock_vec function may fail and return a non-zero error for the following conditions:

DB_LOCK_DEADLOCK
The operation was selected to resolve a deadlock.

EINVAL
An invalid flag value or parameter was specified.

ENOMEM
The maximum number of locks has been reached.

The lock_vec function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the lock_vec function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

See Also

DB_ENV->set_lk_conflicts, DB_ENV->set_lk_detect, DB_ENV->set_lk_max, DB_ENV->set_lk_max_lockers, DB_ENV->set_lk_max_locks, DB_ENV->set_lk_max_objects, lock_detect, lock_get, lock_id, lock_put, lock_stat, and lock_vec.

APIRef

Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 1 a1 1 d6 1 a6 1 Berkeley DB: DB_ENV->lock_vec d14 1 a14 1

DB_ENV->lock_vec

d25 1 a25 1 DB_ENV->lock_vec(DB_ENV *env, u_int32_t locker, u_int32_t flags, d29 2 a30 2

The DB_ENV->lock_vec function atomically obtains and releases one or more locks from the lock table. The DB_ENV->lock_vec function is intended to support d34 1 a34 1

The locker argument specified to DB_ENV->lock_vec is an unsigned d44 1 a44 1

The list array provided to DB_ENV->lock_vec is typedef'd as d55 6 a60 9

DB_LOCK_GET
Get the lock defined by the values of the mode and obj structure fields, for the specified locker. Upon return from DB_ENV->lock_vec, if the lock field is non-NULL, a reference to the acquired lock is stored there. (This reference is invalidated by any call to DB_ENV->lock_vec or DB_ENV->lock_put that releases the lock.)

DB_LOCK_GET_TIMEOUT
Identical to DB_LOCK_GET except that the value in the timeout structure field overrides any previously specified timeout value for this lock. A value of 0 turns off any previously specified timeout. d67 1 a67 1 DB_ENV->lock_vec which appear before the DB_LOCK_PUT_ALL d73 1 a73 1 current call to DB_ENV->lock_vec that appear before the a76 6

DB_LOCK_TIMEOUT
Cause the specified locker to timeout immediately. If the database environment has not configured automatic deadlock detection, the transaction will timeout the next time deadlock detection is performed. As transactions acquire locks on behalf of a single locker ID, timing out the locker ID associated with a transaction will time out the transaction itself. a95 1

u_int32_t timeout;
The lock timeout value. d102 1 a102 1 DB_ENV->lock_vec returns a non-zero value. In addition, if elistp d107 1 a107 1 DB_ENV->lock_vec function may d111 1 a111 1

Otherwise, the DB_ENV->lock_vec function returns a non-zero error value on failure and 0 on success. d113 1 a113 1

The DB_ENV->lock_vec function may fail and return a non-zero error for the following conditions: d123 2 a124 2

The DB_ENV->lock_vec function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->lock_vec function may fail and return d130 1 d134 5 a138 6 DB_ENV->lock_detect, DB_ENV->lock_get, DB_ENV->lock_id, DB_ENV->lock_id_free, DB_ENV->lock_put, DB_ENV->lock_stat, d140 1 a140 1 DB_ENV->lock_vec. @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d29 2 a30 2

The DB_ENV->lock_vec method atomically obtains and releases one or more locks from the lock table. The DB_ENV->lock_vec method is intended to support d40 3 a42 5

DB_LOCK_NOWAIT
If a lock cannot be granted because the requested lock conflicts with an existing lock, return DB_LOCK_NOTGRANTED immediately instead of waiting for the lock to become available. In this case, if non-NULL, elistp identifies the request that was not granted. d92 5 a96 5
DB_LOCK_READ
read (shared)
DB_LOCK_WRITE
write (exclusive)
DB_LOCK_IWRITE
intention to write (shared)
DB_LOCK_IREAD
intention to read (shared)
DB_LOCK_IWR
intention to read and write (shared) d115 7 a121 2

Otherwise, the DB_ENV->lock_vec method returns a non-zero error value on failure and 0 on success. d123 1 a123 1

The DB_ENV->lock_vec method may fail and return a non-zero error for the following conditions: d133 4 a136 6

The DB_ENV->lock_vec method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->lock_vec method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV, DB_LOCK d138 13 a150 1 Locking Subsystem and Related Methods @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d30 2 a31 2

The DB_ENV->lock_vec function atomically obtains and releases one or more locks from the lock table. The DB_ENV->lock_vec function is intended to support d41 5 a45 3

DB_LOCK_NOWAIT
If a lock cannot be immediately granted because the requested lock conflicts with an existing lock, return instead of waiting for the lock to become available. d95 5 a99 5
DB_LOCK_READ
read (shared)
DB_LOCK_WRITE
write (exclusive)
DB_LOCK_IWRITE
intention to write (shared)
DB_LOCK_IREAD
intention to read (shared)
DB_LOCK_IWR
intention to read and write (shared) d118 2 a119 7

If a lock is requested that cannot be immediately granted, and the flags parameter was set to DB_LOCK_NOWAIT, the DB_ENV->lock_vec function may return DB_LOCK_NOTGRANTED. In this case, if non-NULL, elistp identifies the request that was not granted.

Otherwise, the DB_ENV->lock_vec function returns a non-zero error value on failure and 0 on success. d121 1 a121 1

The DB_ENV->lock_vec function may fail and return a non-zero error for the following conditions: d131 6 a136 4

The DB_ENV->lock_vec function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->lock_vec function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d138 1 a138 13 DB_ENV->set_lk_conflicts, DB_ENV->set_lk_detect, DB_ENV->set_lk_max_lockers, DB_ENV->set_lk_max_locks, DB_ENV->set_lk_max_objects, DB_ENV->lock_detect, DB_ENV->lock_get, DB_ENV->lock_id, DB_ENV->lock_id_free, DB_ENV->lock_put, DB_ENV->lock_stat, and DB_ENV->lock_vec. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d29 2 a30 2

The DB_ENV->lock_vec method atomically obtains and releases one or more locks from the lock table. The DB_ENV->lock_vec method is intended to support d40 3 a42 5

DB_LOCK_NOWAIT
If a lock cannot be granted because the requested lock conflicts with an existing lock, return DB_LOCK_NOTGRANTED immediately instead of waiting for the lock to become available. In this case, if non-NULL, elistp identifies the request that was not granted. d92 5 a96 5
DB_LOCK_READ
read (shared)
DB_LOCK_WRITE
write (exclusive)
DB_LOCK_IWRITE
intention to write (shared)
DB_LOCK_IREAD
intention to read (shared)
DB_LOCK_IWR
intention to read and write (shared) d115 7 a121 2

Otherwise, the DB_ENV->lock_vec method returns a non-zero error value on failure and 0 on success. d123 1 a123 1

The DB_ENV->lock_vec method may fail and return a non-zero error for the following conditions: d133 4 a136 6

The DB_ENV->lock_vec method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->lock_vec method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV, DB_LOCK d138 13 a150 1 Locking Subsystem and Related Methods @