Searched refs:arrival (Results 1 – 22 of 22) sorted by relevance
| /linux/drivers/md/dm-vdo/ |
| A D | data-vio.c | 151 u64 arrival; member
593 limiter->arrival = ((bio == NULL) ? U64_MAX : get_arrival_time(bio)); in assign_data_vio()
600 if (limiter->arrival == U64_MAX) in assign_discard_permit()
601 limiter->arrival = get_arrival_time(bio); in assign_discard_permit()
683 if (pool->limiter.arrival < pool->discard_limiter.arrival) { in reuse_or_release_resources()
685 } else if (pool->discard_limiter.arrival < U64_MAX) { in reuse_or_release_resources()
712 if (pool->limiter.arrival == U64_MAX) { in process_release_callback()
716 pool->limiter.arrival = get_arrival_time(bio); in process_release_callback()
775 limiter->arrival = U64_MAX; in initialize_limiter()
|
| /linux/Documentation/networking/ |
| A D | tcp-thin.rst | 15 dependency on the arrival of new data from the application to trigger
|
| A D | xfrm_sync.rst | 35 is not driven by packet arrival.
185 The first packet arrival after a timer expiry will trigger a timeout
|
| A D | ethtool-netlink.rst | 1055 arrival and the various time based delay parameters. By default timers are
1056 expected to limit the max delay between any packet arrival/departure and a
1058 arrival (sometimes delivery of previous interrupt) and reset when interrupt
1071 counted since the first packet arrival in an aggregated block, after which the
|
| A D | rds.rst | 84 its arrival.
|
| A D | timestamping.rst | 362 and out of order arrival.
|
| /linux/net/sctp/ |
| A D | Kconfig | 27 with an option for order-of-arrival delivery of individual user
|
| /linux/drivers/media/common/siano/ |
| A D | smsdvb-main.c | 1104 struct device *device, int arrival) in smsdvb_hotplug() argument
1111 if (!arrival) in smsdvb_hotplug()
|
| A D | smscoreapi.h | 95 struct device *device, int arrival);
|
| A D | smscoreapi.c | 598 struct device *device, int arrival) in smscore_notify_callbacks() argument
606 rc = elem->hotplug(coredev, device, arrival); in smscore_notify_callbacks()
|
| /linux/Documentation/driver-api/nvdimm/ |
| A D | nvdimm.rst | 127 Prior to the arrival of the NFIT, non-volatile memory was described to a
459 one or more "namespace" devices. The arrival of a "namespace" device currently
|
| /linux/Documentation/driver-api/cxl/ |
| A D | memory-devices.rst | 193 by the arrival of a CXL.mem device. I.e. unless and until the PCIe core attaches
|
| /linux/Documentation/scheduler/ |
| A D | sched-deadline.rst | 332 arrival time r_j (the time when the job starts), an amount of computation
337 sporadic with minimum inter-arrival time P is r_{j+1} >= r_j + P. Finally,
344 WCET and its period (or minimum inter-arrival time), and represents
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-power | 176 concurrent arrival of wakeup events. Reading from it returns
|
| /linux/Documentation/filesystems/ |
| A D | coda.rst | 173 arrival of a new message. The notification must be through a mechanism
305 message arrival. The process P is kept waiting on a KernelEvent
|
| /linux/scripts/ |
| A D | spelling.txt | 166 arraival||arrival
|
| /linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| A D | Expedited-Grace-Periods.rst | 307 The next diagram shows the situation after the arrival of Task A and
|
| /linux/drivers/gpu/drm/amd/amdkfd/ |
| A D | kfd_topology.c | 1188 static void kfd_notify_gpu_change(uint32_t gpu_id, int arrival) in kfd_notify_gpu_change() argument
|
| /linux/net/sched/ |
| A D | Kconfig | 375 functionality (aka output commit), wherein upon arrival of a dequeue
|
| /linux/arch/powerpc/ |
| A D | Kconfig | 583 bool "Clear gprs on interrupt arrival"
|
| /linux/Documentation/power/ |
| A D | runtime_pm.rst | 905 synchronize ->runtime_suspend() callbacks with the arrival of I/O requests.
|
| /linux/net/netfilter/ |
| A D | Kconfig | 1640 the packet arrival time (at the machine which netfilter is running)
|
Completed in 76 milliseconds