Home
last modified time | relevance | path

Searched refs:locks (Results 1 – 25 of 44) sorted by relevance

12

/linux-2.4.37.9/Documentation/
Dmandatory.txt13 processes. File locks are applied using the flock() and fcntl() system calls
15 normally a process' responsibility to check for locks on a file it wishes to
35 interface for applying locks just as if they were normal, advisory locks.
71 another process has outstanding mandatory locks. This is in direct
77 HP-UX even disallows open() with O_TRUNC for a file with advisory locks, not
78 just mandatory locks. That would appear to contravene POSIX.1.
81 prevent mandatory locks from being applied to an mmap()'ed file, but HP-UX
82 also disallows advisory locks for such a file. SVID actually specifies the
86 only from mandatory locks - that is what is currently implemented.
89 mandatory locks, so reads and writes to locked files always block when they
[all …]
Dspinlocks.txt9 > use to lock these spin locks from other use as opposed to a (nasty)
93 to mostly read from the shared variables, the reader-writer locks
172 Note that you can be clever with read-write locks and interrupts. For
174 you can use a non-irq version of read locks everywhere - because they
178 For an example of being clever with rw-locks, see the "waitqueue_lock"
181 wake up. So read-locks are safe (which is good: they are very common
182 indeed), while write-locks need to protect themselves against interrupts.
Dlocks.txt42 is to make flock() and fcntl() locks oblivious to each other. Both can
80 + { "mand", 0, MS_MANDLOCK }, /* Allow mandatory locks on this FS */
81 + { "nomand", 1, MS_MANDLOCK }, /* Forbid mandatory locks on this FS */
Dsmp.tex57 locks only. Some modern systems use fine grained locking. Because fine
60 fine grained locking reduces the amount of time locks are held and reduces
88 the locks to cover smaller areas. With the current kernel highly CPU bound
274 the locks, and cannot cause a reschedule, while IRQ 16 is a slow IRQ that
315 compatible). The kernel has all the relevant locks but does not yet
336 the same time without any locks.
Dtty.txt101 take line discipline locks. The same is true of calls from the driver side
/linux-2.4.37.9/drivers/char/
Dsx.h34 long locks; member
51 int locks; member
Dn_r3964.c632 pBlock->locks = 0; in on_receive_block()
1016 pBlock->locks++; in add_msg()
1084 block->locks--; in remove_client_block()
1085 if(block->locks==0) in remove_client_block()
1357 pHeader->locks = 0; in r3964_write()
Dsx.c1005 if (test_and_set_bit (SX_PORT_TRANSMIT_LOCK, &port->locks)) { in sx_transmit_chars()
1066 clear_bit (SX_PORT_TRANSMIT_LOCK, &port->locks); in sx_transmit_chars()
1271 if (test_and_set_bit (SX_BOARD_INTR_LOCK, &board->locks)) { in sx_interrupt()
1293 clear_bit (SX_BOARD_INTR_LOCK, &board->locks); in sx_interrupt()
/linux-2.4.37.9/include/asm-arm/
Dspinlock.h4 #error ARM architecture does not support SMP spin locks
/linux-2.4.37.9/arch/parisc/lib/
DMakefile9 obj-$(CONFIG_SMP) += locks.o
/linux-2.4.37.9/arch/ppc/lib/
DMakefile13 obj-$(CONFIG_SMP) += locks.o
/linux-2.4.37.9/arch/sparc/lib/
DMakefile16 copy_user.o locks.o atomic.o bitops.o debuglocks.o lshrdi3.o \
/linux-2.4.37.9/include/linux/
Dn_r3964.h162 unsigned int locks; /* only used in rx_buffer */ member
Disdn.h582 int locks; /* Number of locks for this driver */ member
Dsched.h385 unsigned int locks; /* How many file locks are being held */ member
/linux-2.4.37.9/drivers/char/rio/
Dhost.h113 long locks; /* long req'd for set_bit --RR */ member
Drio_linux.c510 if (test_and_set_bit (RIO_BOARD_INTR_LOCK, &HostP->locks)) { in rio_interrupt()
521 clear_bit (RIO_BOARD_INTR_LOCK, &HostP->locks); in rio_interrupt()
/linux-2.4.37.9/Documentation/ia64/
DREADME41 o SMP locks cleanup/optimization
/linux-2.4.37.9/fs/
DMakefile15 fcntl.o ioctl.o readdir.o select.o fifo.o locks.o \
/linux-2.4.37.9/Documentation/filesystems/
Dvfs.txt99 assume that these calls are made without any kernel locks being
103 protected by appropriate locks.
190 All methods are called without any locks being held, unless otherwise
263 Again, all methods are called without any locks being held, unless
344 Again, all methods are called without any locks being held, unless
/linux-2.4.37.9/drivers/isdn/
Disdn_common.c88 dev->drv[i]->locks++; in isdn_lock_drivers()
108 if (dev->drv[i]->locks > 0) { in isdn_unlock_drivers()
115 dev->drv[i]->locks--; in isdn_unlock_drivers()
705 while (dev->drv[di]->locks > 0) { in isdn_status_callback()
711 dev->drv[di]->locks--; in isdn_status_callback()
/linux-2.4.37.9/Documentation/DocBook/
DMakefile125 $(TOPDIR)/fs/locks.c \
/linux-2.4.37.9/Documentation/sound/
DChangeLog.multisound41 * More mutex sections for read and write fifos (read + write locks
/linux-2.4.37.9/Documentation/networking/
D8139too.txt321 * Correct some sledgehammer a.k.a. overzealous spin-locks
413 * No longer locks CONFIGx updates
/linux-2.4.37.9/Documentation/vm/
Dlocking73 pagemap_lru_lock spinlocks, and no code asks for memory with these locks

12