| /linux-5.19.10/Documentation/filesystems/ |
| D | automount-support.rst | 42 Automatic expiration of mountpoints is easy, provided you've mounted the
45 To do expiration, you need to follow these steps:
66 The expiration flag is cleared by calls to mntput. This means that expiration
67 will only happen on the second expiration request after the last time the
70 If a mountpoint is moved, it gets removed from the expiration list. If a bind
72 expiration list and will not expire.
75 and the copies of those that are on an expiration list will be added to the
76 same expiration list.
89 mountpoint will not be marked for expiration or unmounted.
97 Again, the expiration flag is cleared every time anything other than umount()
|
| /linux-5.19.10/block/ |
| D | bfq-wf2q.c | 45 bool expiration);
76 bool expiration) in bfq_update_next_in_service() argument
128 next_in_service = bfq_lookup_next_entity(sd, expiration); in bfq_update_next_in_service()
1120 bool requeue, bool expiration) in bfq_activate_requeue_entity() argument
1128 if (!bfq_update_next_in_service(sd, entity, expiration) && in bfq_activate_requeue_entity()
1199 bool expiration) in bfq_deactivate_entity() argument
1224 bfq_update_next_in_service(sd, NULL, expiration); in bfq_deactivate_entity()
1283 if (!bfq_update_next_in_service(sd, entity, expiration) && in bfq_deactivate_entity()
1284 !expiration) in bfq_deactivate_entity()
1425 bool expiration) in bfq_lookup_next_entity() argument
[all …]
|
| D | bfq-iosched.h | 1076 bool ins_into_idle_tree, bool expiration);
1079 bool expiration);
1081 bool expiration);
|
| /linux-5.19.10/tools/testing/selftests/net/ |
| D | toeplitz_client.sh | 11 expiration=$((SECONDS+20))
12 while [[ "${SECONDS}" -lt "${expiration}" ]]
|
| /linux-5.19.10/Documentation/devicetree/bindings/watchdog/ |
| D | marvel.txt | 34 - interrupts : Contains the IRQ for watchdog expiration
|
| D | snps,dw-wdt.yaml | 64 the timer expiration intervals supported by the DW APB Watchdog. Note
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-class-watchdog | 88 expiration of a watchdog timer of AST2400/AST2500 when
109 expiration) the behavior differs as described above.
|
| D | sysfs-devices-power | 198 1000 will cause the autosuspend timer expiration to be rounded
|
| /linux-5.19.10/Documentation/watchdog/ |
| D | mlx-wdt.rst | 59 initial timeout, performed action in expiration and configuration flags.
|
| /linux-5.19.10/Documentation/ABI/stable/ |
| D | sysfs-driver-firmware-zynqmp | 100 bit on FPD WDT expiration. If healthy bit is set by a user
102 healthy bit is not set during FPD WDT expiration, PMUFW will do
|
| /linux-5.19.10/Documentation/dev-tools/ |
| D | kfence.rst | 242 Guarded allocations are set up based on the sample interval. After expiration
246 the next allocation is set up after the expiration of the interval.
|
| /linux-5.19.10/drivers/watchdog/ |
| D | Kconfig | 1111 the machine after its expiration. The expiration time can be
1266 that will reboot the machine after its second expiration. The
1267 expiration time can be configured with the "heartbeat" parameter.
1390 expiration. The expiration time can be configured with the
1755 interrupt. On first expiration of the watchdog, the
1756 interrupt handler pokes it. The second expiration causes an
1757 NMI that prints a message. The third expiration causes a
|
| /linux-5.19.10/Documentation/core-api/ |
| D | timekeeping.rst | 28 used e.g. for key expiration times that need to be synchronized
|
| /linux-5.19.10/drivers/net/wireless/marvell/libertas/ |
| D | host.h | 957 __le32 expiration; member
|
| /linux-5.19.10/Documentation/scheduler/ |
| D | sched-stats.rst | 47 2) This field is a legacy array expiration count field used in the O(1)
|
| D | sched-bwc.rst | 178 For highly-threaded, non-cpu bound applications this non-expiration nuance
|
| /linux-5.19.10/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 178 - add or change the expiration date on itself or any subkey
644 Extending key expiration date
647 The master key has the default expiration date of 2 years from the date
651 To extend the expiration on your key by a year from current date, just
|
| /linux-5.19.10/Documentation/power/ |
| D | runtime_pm.rst | 215 - timer expiration time, in jiffies (if this is different from zero, the
527 is 1000 ms or larger then the expiration time is rounded up to the
529 power.use_autosuspend isn't set, otherwise returns the expiration time
891 returns -EAGAIN or -EBUSY, and if the next autosuspend delay expiration time is
|
| /linux-5.19.10/net/sctp/ |
| D | sm_make_chunk.c | 1706 cookie->c.expiration = ktime_add(asoc->cookie_life, in sctp_pack_cookie()
1836 if (!asoc && ktime_before(bear_cookie->expiration, kt)) { in sctp_unpack_cookie()
1837 suseconds_t usecs = ktime_to_us(ktime_sub(kt, bear_cookie->expiration)); in sctp_unpack_cookie()
|
| /linux-5.19.10/include/net/sctp/ |
| D | structs.h | 297 ktime_t expiration; member
|
| /linux-5.19.10/include/net/netfilter/ |
| D | nf_tables.h | 768 u64 timeout, u64 expiration, gfp_t gfp);
|
| /linux-5.19.10/Documentation/driver-api/surface_aggregator/ |
| D | internal.rst | 263 barriers. Modifications to the timeout reaper work item and expiration date
447 barriers. Modifications to the timeout reaper work item and expiration date
|
| /linux-5.19.10/net/netfilter/ |
| D | nf_tables_api.c | 5485 const u32 *data, u64 timeout, u64 expiration, gfp_t gfp) in nft_set_elem_init() argument
5504 *nft_set_ext_expiration(ext) = get_jiffies_64() + expiration; in nft_set_elem_init()
5505 if (expiration == 0) in nft_set_elem_init()
5850 u64 expiration; in nft_add_set_elem() local
5918 expiration = 0; in nft_add_set_elem()
5923 &expiration); in nft_add_set_elem()
6099 timeout, expiration, GFP_KERNEL_ACCOUNT); in nft_add_set_elem()
|
| /linux-5.19.10/LICENSES/dual/ |
| D | CDDL-1.0 | 297 at the expiration of such 60 day notice period, unless if within
|
| D | MPL-1.1 | 359 Sections 2.1 and/or 2.2 automatically terminate at the expiration of
|