Home
last modified time | relevance | path

Searched refs:expiration (Results 1 – 25 of 31) sorted by relevance

12

/linux-6.12.1/Documentation/filesystems/
Dautomount-support.rst42 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-6.12.1/block/
Dbfq-wf2q.c45 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 …]
Dbfq-iosched.h1151 bool ins_into_idle_tree, bool expiration);
1154 bool expiration);
1155 void bfq_del_bfqq_busy(struct bfq_queue *bfqq, bool expiration);
/linux-6.12.1/tools/testing/selftests/net/
Dtoeplitz_client.sh11 expiration=$((SECONDS+20))
12 while [[ "${SECONDS}" -lt "${expiration}" ]]
/linux-6.12.1/Documentation/devicetree/bindings/watchdog/
Dmarvel.txt34 - interrupts : Contains the IRQ for watchdog expiration
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-class-watchdog101 expiration of a watchdog timer of AST2400/AST2500 when
122 expiration) the behavior differs as described above.
Dsysfs-devices-power198 1000 will cause the autosuspend timer expiration to be rounded
/linux-6.12.1/include/net/netfilter/
Dnf_tables.h814 u64 expiration; member
839 return time_after_eq64(tstamp, READ_ONCE(nft_set_ext_timeout(ext)->expiration)); in __nft_set_elem_expired()
866 u64 timeout, u64 expiration, gfp_t gfp);
1766 u64 expiration; member
1782 nft_trans_container_elem(trans)->expiration
/linux-6.12.1/Documentation/watchdog/
Dmlx-wdt.rst59 initial timeout, performed action in expiration and configuration flags.
/linux-6.12.1/Documentation/ABI/stable/
Dsysfs-driver-firmware-zynqmp100 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-6.12.1/Documentation/dev-tools/
Dkfence.rst249 Guarded allocations are set up based on the sample interval. After expiration
253 the next allocation is set up after the expiration of the interval.
/linux-6.12.1/net/netfilter/
Dnft_dynset.c100 WRITE_ONCE(nft_set_ext_timeout(ext)->expiration, get_jiffies_64() + timeout); in nft_dynset_eval()
Dnf_tables_api.c5833 expires = READ_ONCE(nft_set_ext_timeout(ext)->expiration); in nf_tables_fill_setelem()
6479 u64 timeout, u64 expiration, gfp_t gfp) in nft_set_elem_init() argument
6509 if (expiration == 0) in nft_set_elem_init()
6510 expiration = timeout; in nft_set_elem_init()
6512 nft_set_ext_timeout(ext)->expiration = get_jiffies_64() + expiration; in nft_set_elem_init()
6857 u64 expiration; in nft_add_set_elem() local
6928 expiration = 0; in nft_add_set_elem()
6936 &expiration); in nft_add_set_elem()
6940 if (expiration > timeout) in nft_add_set_elem()
7117 timeout, expiration, GFP_KERNEL_ACCOUNT); in nft_add_set_elem()
[all …]
/linux-6.12.1/Documentation/core-api/
Dtimekeeping.rst28 used e.g. for key expiration times that need to be synchronized
/linux-6.12.1/drivers/watchdog/
DKconfig1194 the machine after its expiration. The expiration time can be
1350 that will reboot the machine after its second expiration. The
1351 expiration time can be configured with the "heartbeat" parameter.
1474 expiration. The expiration time can be configured with the
1835 interrupt. On first expiration of the watchdog, the
1836 interrupt handler pokes it. The second expiration causes an
1837 NMI that prints a message. The third expiration causes a
/linux-6.12.1/drivers/net/wireless/marvell/libertas/
Dhost.h957 __le32 expiration; member
/linux-6.12.1/Documentation/scheduler/
Dsched-stats.rst52 2) This field is a legacy array expiration count field used in the O(1)
Dsched-bwc.rst178 For highly-threaded, non-cpu bound applications this non-expiration nuance
/linux-6.12.1/Documentation/process/
Dmaintainer-pgp-guide.rst159 - add or change the expiration date on itself or any subkey
603 Extending key expiration date
606 The Certify key has the default expiration date of 2 years from the date
610 To extend the expiration on your key by a year from current date, just
/linux-6.12.1/Documentation/power/
Druntime_pm.rst215 - timer expiration time, in jiffies (if this is different from zero, the
530 is 1000 ms or larger then the expiration time is rounded up to the
532 power.use_autosuspend isn't set, otherwise returns the expiration time
896 returns -EAGAIN or -EBUSY, and if the next autosuspend delay expiration time is
/linux-6.12.1/net/sctp/
Dsm_make_chunk.c1706 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-6.12.1/Documentation/driver-api/surface_aggregator/
Dinternal.rst263 barriers. Modifications to the timeout reaper work item and expiration date
447 barriers. Modifications to the timeout reaper work item and expiration date
/linux-6.12.1/include/net/sctp/
Dstructs.h294 ktime_t expiration; member
/linux-6.12.1/LICENSES/dual/
DCDDL-1.0297 at the expiration of such 60 day notice period, unless if within
DMPL-1.1359 Sections 2.1 and/or 2.2 automatically terminate at the expiration of

12