| /kernel/linux/linux-5.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()
|
| D | vfs.rst | 1292 expiration list in the case of failure. The vfsmount should be
1293 returned with 2 refs on it to prevent automatic expiration - the
|
| /kernel/linux/linux-5.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()
1138 bool requeue, bool expiration) in bfq_activate_requeue_entity() argument
1146 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 | 1049 bool ins_into_idle_tree, bool expiration);
1052 bool expiration);
1054 bool expiration);
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/watchdog/ |
| D | marvel.txt | 34 - interrupts : Contains the IRQ for watchdog expiration
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.10/Documentation/watchdog/ |
| D | mlx-wdt.rst | 59 initial timeout, performed action in expiration and configuration flags.
|
| /kernel/linux/linux-5.10/drivers/visorbus/ |
| D | visorchipset.c | 104 unsigned long expiration; member
885 req->expiration = parahotplug_next_expiration(); in parahotplug_request_create()
1486 if (!time_after_eq(jiffies, req->expiration)) in parahotplug_process_list()
|
| /kernel/linux/linux-5.10/drivers/watchdog/ |
| D | Kconfig | 1099 the machine after its expiration. The expiration time can be
1259 that will reboot the machine after its second expiration. The
1260 expiration time can be configured with the "heartbeat" parameter.
1383 expiration. The expiration time can be configured with the
1747 interrupt. On first expiration of the watchdog, the
1748 interrupt handler pokes it. The second expiration causes an
1749 NMI that prints a message. The third expiration causes a
|
| /kernel/linux/linux-5.10/drivers/net/wireless/marvell/libertas/ |
| D | host.h | 953 __le32 expiration; member
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | timekeeping.rst | 28 used e.g. for key expiration times that need to be synchronized
|
| /kernel/linux/linux-5.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 | 118 For highly-threaded, non-cpu bound applications this non-expiration nuance
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | runtime_pm.rst | 215 - timer expiration time, in jiffies (if this is different from zero, the
513 is 1000 ms or larger then the expiration time is rounded up to the
515 power.use_autosuspend isn't set, otherwise returns the expiration time
868 returns -EAGAIN or -EBUSY, and if the next autosuspend delay expiration time is
|
| /kernel/linux/linux-5.10/net/sctp/ |
| D | sm_make_chunk.c | 1661 cookie->c.expiration = ktime_add(asoc->cookie_life, in sctp_pack_cookie()
1791 if (!asoc && ktime_before(bear_cookie->expiration, kt)) { in sctp_unpack_cookie()
1792 suseconds_t usecs = ktime_to_us(ktime_sub(kt, bear_cookie->expiration)); in sctp_unpack_cookie()
|
| /kernel/linux/linux-5.10/include/net/sctp/ |
| D | structs.h | 293 ktime_t expiration; member
|
| /kernel/linux/linux-5.10/include/net/netfilter/ |
| D | nf_tables.h | 681 u64 timeout, u64 expiration, gfp_t gfp);
|
| /kernel/linux/linux-5.10/net/netfilter/ |
| D | nf_tables_api.c | 5098 const u32 *data, u64 timeout, u64 expiration, gfp_t gfp) in nft_set_elem_init() argument
5116 *nft_set_ext_expiration(ext) = get_jiffies_64() + expiration; in nft_set_elem_init()
5117 if (expiration == 0) in nft_set_elem_init()
5207 u64 expiration; in nft_add_set_elem() local
5257 expiration = 0; in nft_add_set_elem()
5262 &expiration); in nft_add_set_elem()
5376 timeout, expiration, GFP_KERNEL); in nft_add_set_elem()
|
| D | Kconfig | 885 The remaining time for expiration can be read via sysfs.
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | power-management.rst | 460 busy and therefore the next autosuspend idle-delay expiration should
|