Searched refs:surprise (Results 1 – 8 of 8) sorted by relevance
| /linux/Documentation/filesystems/ |
| H A D | inotify.rst | 61 example, love it. Trust me, I asked. It is not a surprise: Who'd want
|
| /linux/block/ |
| H A D | bdev.c | 1255 void bdev_mark_dead(struct block_device *bdev, bool surprise) in bdev_mark_dead() argument
1259 bdev->bd_holder_ops->mark_dead(bdev, surprise); in bdev_mark_dead()
|
| /linux/fs/ |
| H A D | super.c | 1453 static void fs_bdev_mark_dead(struct block_device *bdev, bool surprise) in fs_bdev_mark_dead() argument
1472 if (!surprise) in fs_bdev_mark_dead()
|
| /linux/tools/memory-model/Documentation/ |
| H A D | locking.txt | 118 no surprise that "r2" can be zero, and a quick herd7 run confirms this.
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | concepts.rst | 179 repurposing them is called (surprise!) `reclaim`. Linux can reclaim
|
| /linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 1116 It often comes as a surprise that many algorithms do not require a
2101 accumulation by these kthreads. This requirement was no surprise, but
2103 built with ``CONFIG_NO_HZ_FULL=y`` `did come as a surprise
2131 needed fix, so this surprise requirement was relatively painless.
2429 surprise, the sub-100-microsecond real-time latency budget `applies to
2448 Although the need for ``rcutorture`` was no surprise, the current
|
| /linux/Documentation/scsi/ |
| H A D | st.rst | 279 cause a surprise when moving from 2.4. There small writes (e.g., tar without
|
| /linux/Documentation/ |
| H A D | memory-barriers.txt | 1673 surprise if some other CPU might have stored to variable 'a' in the
|