| /linux/Documentation/filesystems/ |
| H A 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/block/ |
| H A 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()
1088 bool requeue, bool expiration) in bfq_activate_requeue_entity() argument
1093 expiration) && !requeue) in bfq_activate_requeue_entity()
1163 bool expiration) in bfq_deactivate_entity() argument
1188 bfq_update_next_in_service(sd, NULL, expiration); in bfq_deactivate_entity()
1247 if (!bfq_update_next_in_service(sd, entity, expiration) && in bfq_deactivate_entity()
1248 !expiration) in bfq_deactivate_entity()
1391 bool expiration) in bfq_lookup_next_entity() argument
[all …]
|
| H A D | bfq-iosched.h | 1150 bool ins_into_idle_tree, bool expiration);
1153 bool expiration);
1154 void bfq_del_bfqq_busy(struct bfq_queue *bfqq, bool expiration);
|
| /linux/tools/testing/selftests/net/ |
| H A D | toeplitz_client.sh | |
| /linux/drivers/clocksource/ |
| H A D | timer-tegra186.c | 233 u32 expiration, val; in tegra186_wdt_get_timeleft() local
257 expiration = FIELD_GET(WDTSR_CURRENT_EXPIRATION_COUNT, val); in tegra186_wdt_get_timeleft()
258 if (WARN_ON_ONCE(expiration > 4)) in tegra186_wdt_get_timeleft()
280 timeleft += (wdt->base.timeout * (USEC_PER_SEC / 5)) * (4 - expiration); in tegra186_wdt_get_timeleft()
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-watchdog | 101 expiration of a watchdog timer of AST2400/AST2500 when
122 expiration) the behavior differs as described above.
|
| /linux/Documentation/watchdog/ |
| H A D | mlx-wdt.rst | 59 initial timeout, performed action in expiration and configuration flags.
|
| /linux/include/net/netfilter/ |
| H A D | nf_tables.h | 813 u64 expiration; member
838 return time_after_eq64(tstamp, READ_ONCE(nft_set_ext_timeout(ext)->expiration)); in __nft_set_elem_expired()
865 u64 timeout, u64 expiration, gfp_t gfp);
1794 u64 expiration; member
|
| /linux/Documentation/ABI/stable/ |
| H A 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/net/netfilter/ |
| H A D | nft_dynset.c | 108 WRITE_ONCE(nft_set_ext_timeout(ext)->expiration, get_jiffies_64() + timeout); in nft_dynset_eval()
|
| H A D | nf_tables_api.c | 6186 expires = READ_ONCE(nft_set_ext_timeout(ext)->expiration); in nf_tables_fill_setelem()
6772 u64 timeout, u64 expiration, gfp_t gfp) in nft_set_elem_init() argument
6802 if (expiration == 0) in nft_set_elem_init()
6803 expiration = timeout; in nft_set_elem_init()
6805 nft_set_ext_timeout(ext)->expiration = get_jiffies_64() + expiration; in nft_set_elem_init()
7072 WRITE_ONCE(nft_set_ext_timeout(ext)->expiration, get_jiffies_64() + update->expiration); in nft_trans_elem_update()
7254 u64 expiration; in nft_add_set_elem() local
7325 expiration = 0; in nft_add_set_elem()
7333 &expiration); in nft_add_set_elem()
7337 if (expiration > timeout) in nft_add_set_elem()
[all …]
|
| /linux/Documentation/core-api/ |
| H A D | timekeeping.rst | 28 used e.g. for key expiration times that need to be synchronized
|
| /linux/drivers/net/wireless/marvell/libertas/ |
| H A D | host.h | 957 __le32 expiration; member
|
| /linux/Documentation/driver-api/surface_aggregator/ |
| H A 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/LICENSES/dual/ |
| H A D | CDDL-1.0 | 297 at the expiration of such 60 day notice period, unless if within
|
| H A D | MPL-1.1 | 359 Sections 2.1 and/or 2.2 automatically terminate at the expiration of
|
| /linux/Documentation/driver-api/usb/ |
| H A D | power-management.rst | 460 busy and therefore the next autosuspend idle-delay expiration should
|