| /linux/Documentation/networking/ |
| H A D | page_pool.rst | 90 Driver is always responsible for syncing the pages for the CPU.
91 Drivers may choose to take care of syncing for the device as well
96 of the buffer has to be synced. This allows the core to avoid syncing the entire
100 of the buffer is not touched by the device, so to avoid syncing
115 Note that the syncing parameters are for the **entire page**, even if
|
| H A D | switchdev.rst | 265 Learning_sync attribute enables syncing of the learned/forgotten FDB entry to
|
| /linux/Documentation/ABI/testing/ |
| H A 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/drivers/net/ethernet/mellanox/mlx5/core/lib/ |
| H A 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/sound/oss/dmasound/ |
| H A D | dmasound_core.c | 523 sq->syncing = 0; in sq_setup()
583 this will mimic the behaviour of syncing and allow the sq_play() to in sq_write()
593 write_sq.syncing &= ~2 ; /* take out POST status */ in sq_write()
846 write_sq.syncing |= 1; in sq_fsync()
869 write_sq.syncing = 0 ; in sq_fsync()
1019 write_sq.syncing |= 0x2 ; in sq_ioctl()
1309 write_sq.busy, write_sq.syncing, write_sq.locked, write_sq.xruns) ; in state_open()
|
| H A D | dmasound.h | 234 int busy, syncing, xruns, died; member
|
| H A D | dmasound_atari.c | 1219 !write_sq.syncing) { in AtaPlay()
1234 !write_sq.syncing) { in AtaPlay()
1249 !write_sq.syncing) { in AtaPlay()
|
| H A D | dmasound_q40.c | 448 if (write_sq.count <= 1 && write_sq.rear_size < write_sq.block_size && !write_sq.syncing) { in Q40Play()
|
| /linux/tools/testing/kunit/test_data/ |
| H A D | test_kernel_panic_interrupt.log | 21 [ 0.060000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| H A D | test_config_printk_time.log | 27 [ 0.060000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| H A D | test_pound_sign.log | 29 [ 0.060000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| H A 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)
|
| H A D | test_pound_no_prefix.log | 29 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| H A D | test_multiple_prefixes.log | 27 [ 0.060000][ T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98…
|
| H A D | test_interrupted_tap_output.log | 33 [ 0.060000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
|
| H A 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/Documentation/i2c/ |
| H A D | dma-considerations.rst | 59 message or not. No syncing is needed in cases setting up DMA had an error and
|
| /linux/drivers/md/ |
| H A D | raid5.c | 3710 s->syncing = 0; in handle_failed_sync()
3790 if (s->syncing || s->expanding || in need_this_block()
3792 /* When syncing, or expanding we read everything. in need_this_block()
3953 disk_idx, s->syncing); in handle_stripe_fill()
4799 * else if we are after resync_offset, we must be syncing
4800 * else if MD_RECOVERY_REQUESTED is set, we also are syncing.
4808 s->syncing = 1; in clear_batch_ready()
4993 if (s.syncing || s.expanding || s.expanded || in handle_stripe()
5026 if (s.syncing + s.replacing) in handle_stripe()
5103 || (s.syncing in handle_stripe()
[all...] |
| /linux/Documentation/virt/uml/ |
| H A D | user_mode_linux_howto_v2.rst | 797 no syncing of disks and no clean shutdown of userspace. So, they are
|