Lines Matching refs:locking

8 0. Why you should avoid mandatory locking
27 1. What is  mandatory locking?
30 Mandatory locking is kernel enforced file locking, as opposed to the more usual
31 cooperative file locking used to guarantee sequential access to files among
42 "advisory" locking scheme. However, the world isn't perfect, and there's
46 with a "mandatory" locking scheme, whereby the operating system kernel would
51 The System V mandatory locking scheme was intended to have as little impact as
53 as candidates for mandatory locking, and using the existing fcntl()/lockf()
57 the whole truth. System V locking is based on fcntl(). The granularity of
58 fcntl() is such that it allows the locking of byte ranges in files, in addition
59 to entire files, so the mandatory locking rules also have byte level
62 Note 2: POSIX.1 does not specify any scheme for mandatory locking, despite
63 borrowing the fcntl() locking scheme from System V. The mandatory locking
66 2. Marking a file for mandatory locking
69 A file is marked as a candidate for mandatory locking by setting the group-id
83 I have considered the implementations of mandatory locking available with
104 In my opinion only MAP_SHARED mappings should be immune from locking, and then
118 1. Mandatory locks can only be applied via the fcntl()/lockf() locking
152 for the purposes of mandatory locking.