| /Linux-v5.4/Documentation/filesystems/ |
| D | automount-support.txt | 37 Automatic expiration of mountpoints is easy, provided you've mounted the
40 To do expiration, you need to follow these steps:
60 The expiration flag is cleared by calls to mntput. This means that expiration
61 will only happen on the second expiration request after the last time the
64 If a mountpoint is moved, it gets removed from the expiration list. If a bind
66 expiration list and will not expire.
69 and the copies of those that are on an expiration list will be added to the
70 same expiration list.
84 mountpoint will not be marked for expiration or unmounted.
92 Again, the expiration flag is cleared every time anything other than umount()
|
| D | vfs.rst | 1277 expiration list in the case of failure. The vfsmount should be
1278 returned with 2 refs on it to prevent automatic expiration - the
|
| /Linux-v5.4/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()
1141 bool requeue, bool expiration) in bfq_activate_requeue_entity() argument
1149 if (!bfq_update_next_in_service(sd, entity, expiration) && in bfq_activate_requeue_entity()
1217 bool expiration) in bfq_deactivate_entity() argument
1242 bfq_update_next_in_service(sd, NULL, expiration); in bfq_deactivate_entity()
1301 if (!bfq_update_next_in_service(sd, entity, expiration) && in bfq_deactivate_entity()
1302 !expiration) in bfq_deactivate_entity()
1443 bool expiration) in bfq_lookup_next_entity() argument
[all …]
|
| D | bfq-iosched.h | 1041 bool ins_into_idle_tree, bool expiration);
1044 bool expiration);
1046 bool expiration);
|
| /Linux-v5.4/Documentation/devicetree/bindings/watchdog/ |
| D | marvel.txt | 34 - interrupts : Contains the IRQ for watchdog expiration
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-watchdog | 83 expiration of a watchdog timer of AST2400/AST2500 when
101 expiration) the behavior differs as described above.
|
| D | sysfs-devices-power | 198 1000 will cause the autosuspend timer expiration to be rounded
|
| /Linux-v5.4/Documentation/watchdog/ |
| D | mlx-wdt.rst | 50 initial timeout, performed action in expiration and configuration flags.
|
| /Linux-v5.4/drivers/visorbus/ |
| D | visorchipset.c | 104 unsigned long expiration; member
885 req->expiration = parahotplug_next_expiration(); in parahotplug_request_create()
1483 if (!time_after_eq(jiffies, req->expiration)) in parahotplug_process_list()
|
| /Linux-v5.4/drivers/watchdog/ |
| D | Kconfig | 1059 the machine after its expiration. The expiration time can be
1218 that will reboot the machine after its second expiration. The
1219 expiration time can be configured with the "heartbeat" parameter.
1342 expiration. The expiration time can be configured with the
1702 interrupt. On first expiration of the watchdog, the
1703 interrupt handler pokes it. The second expiration causes an
1704 NMI that prints a message. The third expiration causes a
|
| /Linux-v5.4/drivers/net/wireless/marvell/libertas/ |
| D | host.h | 953 __le32 expiration; member
|
| /Linux-v5.4/Documentation/core-api/ |
| D | timekeeping.rst | 28 used e.g. for key expiration times that need to be synchronized
|
| /Linux-v5.4/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 | 118 For highly-threaded, non-cpu bound applications this non-expiration nuance
|
| /Linux-v5.4/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-v5.4/Documentation/power/ |
| D | runtime_pm.rst | 215 - timer expiration time, in jiffies (if this is different from zero, the
507 is 1000 ms or larger then the expiration time is rounded up to the
509 power.use_autosuspend isn't set, otherwise returns the expiration time
862 returns -EAGAIN or -EBUSY, and if the next autosuspend delay expiration time is
|
| /Linux-v5.4/include/net/netfilter/ |
| D | nf_tables.h | 659 u64 timeout, u64 expiration, gfp_t gfp);
|
| /Linux-v5.4/net/sctp/ |
| D | sm_make_chunk.c | 1657 cookie->c.expiration = ktime_add(asoc->cookie_life, in sctp_pack_cookie()
1794 if (!asoc && ktime_before(bear_cookie->expiration, kt)) { in sctp_unpack_cookie()
1795 suseconds_t usecs = ktime_to_us(ktime_sub(kt, bear_cookie->expiration)); in sctp_unpack_cookie()
|
| /Linux-v5.4/net/netfilter/ |
| D | nf_tables_api.c | 4384 u64 timeout, u64 expiration, gfp_t gfp) in nft_set_elem_init() argument
4400 *nft_set_ext_expiration(ext) = get_jiffies_64() + expiration; in nft_set_elem_init()
4401 if (expiration == 0) in nft_set_elem_init()
4468 u64 expiration; in nft_add_set_elem() local
4512 expiration = 0; in nft_add_set_elem()
4517 &expiration); in nft_add_set_elem()
4604 timeout, expiration, GFP_KERNEL); in nft_add_set_elem()
|
| D | Kconfig | 892 The remaining time for expiration can be read via sysfs.
|
| /Linux-v5.4/include/net/sctp/ |
| D | structs.h | 289 ktime_t expiration; member
|
| /Linux-v5.4/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
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | power-management.rst | 460 busy and therefore the next autosuspend idle-delay expiration should
|
| /Linux-v5.4/Documentation/networking/ |
| D | ip-sysctl.txt | 1804 global addresses with no expiration time are not flushed.
|
