| /Linux-v6.6/Documentation/networking/ |
| D | page_pool.rst | 69 Driver is always responsible for syncing the pages for the CPU.
70 Drivers may choose to take care of syncing for the device as well
75 of the buffer has to be synced. This allows the core to avoid syncing the entire
79 of the buffer is not touched by the device, so to avoid syncing
94 Note that the syncing parameters are for the entire page.
|
| D | xfrm_sync.rst | 11 The end goal for syncing is to be able to insert attributes + generate
|
| D | switchdev.rst | 265 Learning_sync attribute enables syncing of the learned/forgotten FDB entry to
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-class-devlink | 82 and has no impact on the binding, unbinding and syncing the
114 affecting the syncing of the hardware and software state of the
128 '1' means the device link will only affect the syncing of
|
| /Linux-v6.6/drivers/net/ethernet/mellanox/mlx5/core/lib/ |
| D | crypto.c | 46 bool syncing; member
422 return !pool->syncing && in mlx5_crypto_dek_need_sync()
447 pool->syncing = true; in mlx5_crypto_dek_free_locked()
460 if (pool->syncing) in mlx5_crypto_dek_pool_push()
599 pool->syncing = false; in mlx5_crypto_dek_sync_work_fn()
|
| /Linux-v6.6/tools/testing/kunit/test_data/ |
| D | test_kernel_panic_interrupt.log | 21 [ 0.060000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| D | test_config_printk_time.log | 27 [ 0.060000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| D | test_output_with_prefix_isolated_correctly.log | 28 [ 0.060000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| D | test_pound_sign.log | 29 [ 0.060000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| D | test_pound_no_prefix.log | 29 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| D | test_multiple_prefixes.log | 27 [ 0.060000][ T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98…
|
| D | test_interrupted_tap_output.log | 33 [ 0.060000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| D | test_is_test_passed-no_tests_run_no_header.log | 75 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| /Linux-v6.6/sound/oss/dmasound/ |
| D | dmasound_core.c | 526 sq->syncing = 0; in sq_setup()
601 write_sq.syncing &= ~2 ; /* take out POST status */ in sq_write()
849 write_sq.syncing |= 1; in sq_fsync()
872 write_sq.syncing = 0 ; in sq_fsync()
1022 write_sq.syncing |= 0x2 ; in sq_ioctl()
1313 write_sq.busy, write_sq.syncing, write_sq.locked, write_sq.xruns) ; in state_open()
|
| D | dmasound.h | 234 int busy, syncing, xruns, died; member
|
| D | dmasound_atari.c | 1219 !write_sq.syncing) { in AtaPlay()
1234 !write_sq.syncing) { in AtaPlay()
1249 !write_sq.syncing) { in AtaPlay()
|
| D | dmasound_q40.c | 448 if (write_sq.count <= 1 && write_sq.rear_size < write_sq.block_size && !write_sq.syncing) { in Q40Play()
|
| D | dmasound_paula.c | 543 write_sq.rear_size < write_sq.block_size && !write_sq.syncing) { in AmiPlay()
|
| /Linux-v6.6/Documentation/networking/caif/ |
| D | caif.rst | 83 byte 02 is start of frame extension (STX) used for re-syncing
|
| /Linux-v6.6/drivers/md/ |
| D | raid5.h | 284 int syncing, expanding, expanded, replacing; member
|
| D | raid5.c | 1253 if (s->syncing || s->expanding || s->expanded in ops_run_io()
1316 if (s->syncing || s->expanding || s->expanded in ops_run_io()
3783 s->syncing = 0; in handle_failed_sync()
3860 if (s->syncing || s->expanding || in need_this_block()
4021 disk_idx, s->syncing); in fetch_block()
4882 s->syncing = 1; in analyse_stripe()
5054 if (s.syncing || s.expanding || s.expanded || in handle_stripe()
5087 if (s.syncing + s.replacing) in handle_stripe()
5164 || (s.syncing && (s.uptodate + s.compute < disks)) in handle_stripe()
5221 (s.syncing && s.locked == 0 && in handle_stripe()
[all …]
|
| /Linux-v6.6/Documentation/i2c/ |
| D | dma-considerations.rst | 59 message or not. No syncing is needed in cases setting up DMA had an error and
|
| /Linux-v6.6/Documentation/kernel-hacking/ |
| D | false-sharing.rst | 174 or reasonably increase the threshold for syncing per-cpu data to
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | sysrq.rst | 90 ``b`` Will immediately reboot the system without syncing or unmounting
|
| /Linux-v6.6/Documentation/admin-guide/laptops/ |
| D | laptop-mode.rst | 203 * In syslog.conf, you can prefix entries with a dash `-` to omit syncing the
|
