Searched refs:expiration (Results 1 – 14 of 14) sorted by relevance
| /linux-4.4.14/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.txt | 1037 mountpoint and will remove the vfsmount from its expiration list in
1039 it to prevent automatic expiration - the caller will clean up the
|
| /linux-4.4.14/Documentation/devicetree/bindings/watchdog/ |
| D | marvel.txt | 34 - interrupts : Contains the IRQ for watchdog expiration
|
| /linux-4.4.14/block/ |
| D | Kconfig.iosched | 20 CSCAN service with FIFO expiration of requests, switching to
|
| /linux-4.4.14/drivers/watchdog/ |
| D | Kconfig | 672 the machine after its expiration. The expiration time can be
830 that will reboot the machine after its second expiration. The
831 expiration time can be configured with the "heartbeat" parameter.
953 expiration. The expiration time can be configured with the
1264 interrupt. On first expiration of the watchdog, the
1265 interrupt handler pokes it. The second expiration causes an
1266 NMI that prints a message. The third expiration causes a
|
| /linux-4.4.14/drivers/staging/unisys/visorbus/ |
| D | visorchipset.c | 208 unsigned long expiration; member
1539 req->expiration = parahotplug_next_expiration(); in parahotplug_request_create()
1600 if (!time_after_eq(jiffies, req->expiration)) in parahotplug_process_list()
|
| /linux-4.4.14/drivers/net/wireless/libertas/ |
| D | host.h | 952 __le32 expiration; member
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-stats.txt | 41 2) This field is a legacy array expiration count field used in the O(1)
|
| /linux-4.4.14/Documentation/power/ |
| D | runtime_pm.txt | 208 - timer expiration time, in jiffies (if this is different from zero, the
488 is 1000 ms or larger then the expiration time is rounded up to the
490 power.use_autosuspend isn't set, otherwise returns the expiration time
836 returns -EAGAIN or -EBUSY, and if the next autosuspend delay expiration time is
|
| /linux-4.4.14/net/sctp/ |
| D | sm_make_chunk.c | 1654 cookie->c.expiration = ktime_add(asoc->cookie_life, in sctp_pack_cookie()
1785 if (!asoc && ktime_before(bear_cookie->expiration, kt)) { in sctp_unpack_cookie()
1797 suseconds_t usecs = ktime_to_us(ktime_sub(kt, bear_cookie->expiration)); in sctp_unpack_cookie()
|
| /linux-4.4.14/include/net/sctp/ |
| D | structs.h | 286 ktime_t expiration; member
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-devices-power | 198 1000 will cause the autosuspend timer expiration to be rounded
|
| /linux-4.4.14/Documentation/usb/ |
| D | power-management.txt | 451 busy and therefore the next autosuspend idle-delay expiration should
|
| /linux-4.4.14/net/netfilter/ |
| D | Kconfig | 748 The remaining time for expiration can be read via sysfs.
|