Home
last modified time | relevance | path

Searched refs:surprise (Results 1 – 10 of 10) sorted by relevance

/linux/Documentation/filesystems/
H A Dinotify.rst61 example, love it. Trust me, I asked. It is not a surprise: Who'd want
/linux/block/
H A Dbdev.c1238 void bdev_mark_dead(struct block_device *bdev, bool surprise) in bdev_mark_dead() argument
1242 bdev->bd_holder_ops->mark_dead(bdev, surprise); in bdev_mark_dead()
H A Dgenhd.c631 static void blk_report_disk_dead(struct gendisk *disk, bool surprise) in blk_report_disk_dead() argument
649 bdev_mark_dead(bdev, surprise); in blk_report_disk_dead()
/linux/tools/memory-model/Documentation/
H A Dlocking.txt118 no surprise that "r2" can be zero, and a quick herd7 run confirms this.
/linux/fs/
H A Dsuper.c1454 static void fs_bdev_mark_dead(struct block_device *bdev, bool surprise) in fs_bdev_mark_dead() argument
1473 if (!surprise) in fs_bdev_mark_dead()
/linux/Documentation/admin-guide/mm/
H A Dconcepts.rst179 repurposing them is called (surprise!) `reclaim`. Linux can reclaim
/linux/fs/bcachefs/
H A Dsuper.c2288 static void bch2_fs_bdev_mark_dead(struct block_device *bdev, bool surprise) in bch2_fs_bdev_mark_dead() argument
2314 if (!surprise) in bch2_fs_bdev_mark_dead()
/linux/Documentation/RCU/Design/Requirements/
H A DRequirements.rst1116 It often comes as a surprise that many algorithms do not require a
2105 accumulation by these kthreads. This requirement was no surprise, but
2107 built with ``CONFIG_NO_HZ_FULL=y`` `did come as a surprise
2135 needed fix, so this surprise requirement was relatively painless.
2433 surprise, the sub-100-microsecond real-time latency budget `applies to
2452 Although the need for ``rcutorture`` was no surprise, the current
/linux/Documentation/scsi/
H A Dst.rst279 cause a surprise when moving from 2.4. There small writes (e.g., tar without
/linux/Documentation/
H A Dmemory-barriers.txt1673 surprise if some other CPU might have stored to variable 'a' in the