Searched refs:surprise (Results 1 – 11 of 11) sorted by relevance
| /Linux-v6.6/block/ |
| D | bdev.c | 959 void bdev_mark_dead(struct block_device *bdev, bool surprise) in bdev_mark_dead() argument
963 bdev->bd_holder_ops->mark_dead(bdev, surprise); in bdev_mark_dead()
|
| D | genhd.c | 557 static void blk_report_disk_dead(struct gendisk *disk, bool surprise) in blk_report_disk_dead() argument
568 bdev_mark_dead(bdev, surprise); in blk_report_disk_dead()
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | inotify.rst | 61 example, love it. Trust me, I asked. It is not a surprise: Who'd want
|
| /Linux-v6.6/include/linux/ |
| D | blkdev.h | 755 void bdev_mark_dead(struct block_device *bdev, bool surprise);
1465 void (*mark_dead)(struct block_device *bdev, bool surprise);
|
| /Linux-v6.6/tools/memory-model/Documentation/ |
| D | locking.txt | 113 no surprise that "r2" can be zero, and a quick herd7 run confirms this.
|
| /Linux-v6.6/fs/ |
| D | super.c | 1440 static void fs_bdev_mark_dead(struct block_device *bdev, bool surprise) in fs_bdev_mark_dead() argument
1450 if (!surprise) in fs_bdev_mark_dead()
|
| /Linux-v6.6/Documentation/admin-guide/mm/ |
| D | concepts.rst | 179 repurposing them is called (surprise!) `reclaim`. Linux can reclaim
|
| /Linux-v6.6/Documentation/RCU/ |
| D | rcubarrier.rst | 343 in later surprise bugs when the implementation changes.
|
| /Linux-v6.6/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 1116 It often comes as a surprise that many algorithms do not require a
1977 accumulation by these kthreads. This requirement was no surprise, but
1979 built with ``CONFIG_NO_HZ_FULL=y`` `did come as a surprise
2007 needed fix, so this surprise requirement was relatively painless.
2305 surprise, the sub-100-microsecond real-time latency budget `applies to
2324 Although the need for ``rcutorture`` was no surprise, the current
|
| /Linux-v6.6/Documentation/scsi/ |
| D | st.rst | 274 cause a surprise when moving from 2.4. There small writes (e.g., tar without
|
| /Linux-v6.6/Documentation/ |
| D | memory-barriers.txt | 1666 surprise if some other CPU might have stored to variable 'a' in the
|
