Searched refs:expiration (Results 1 – 14 of 14) sorted by relevance
| /linux-4.1.27/Documentation/filesystems/ |
| D | automount-support.txt | 33 should also be given the location of an expiration list (see further
63 Automatic expiration of mountpoints is easy, provided you've mounted the
66 To do expiration, you need to follow these steps:
85 The expiration flag is cleared by calls to mntput. This means that expiration
86 will only happen on the second expiration request after the last time the
89 If a mountpoint is moved, it gets removed from the expiration list. If a bind
91 expiration list and will not expire.
94 and the copies of those that are on an expiration list will be added to the
95 same expiration list.
109 mountpoint will not be marked for expiration or unmounted.
[all …]
|
| D | vfs.txt | 1030 mountpoint and will remove the vfsmount from its expiration list in
1032 it to prevent automatic expiration - the caller will clean up the
|
| /linux-4.1.27/Documentation/devicetree/bindings/watchdog/ |
| D | marvel.txt | 34 - interrupts : Contains the IRQ for watchdog expiration
|
| /linux-4.1.27/block/ |
| D | Kconfig.iosched | 20 CSCAN service with FIFO expiration of requests, switching to
|
| /linux-4.1.27/drivers/watchdog/ |
| D | Kconfig | 608 the machine after its expiration. The expiration time can be
764 that will reboot the machine after its second expiration. The
765 expiration time can be configured with the "heartbeat" parameter.
887 expiration. The expiration time can be configured with the
1198 interrupt. On first expiration of the watchdog, the
1199 interrupt handler pokes it. The second expiration causes an
1200 NMI that prints a message. The third expiration causes a
|
| /linux-4.1.27/drivers/staging/unisys/visorchipset/ |
| D | visorchipset_main.c | 211 unsigned long expiration; member
1486 req->expiration = parahotplug_next_expiration(); in parahotplug_request_create()
1547 if (!time_after_eq(jiffies, req->expiration)) in parahotplug_process_list()
|
| /linux-4.1.27/drivers/net/wireless/libertas/ |
| D | host.h | 952 __le32 expiration; member
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | sched-stats.txt | 41 2) This field is a legacy array expiration count field used in the O(1)
|
| /linux-4.1.27/Documentation/power/ |
| D | runtime_pm.txt | 208 - timer expiration time, in jiffies (if this is different from zero, the
492 is 1000 ms or larger then the expiration time is rounded up to the
494 power.use_autosuspend isn't set, otherwise returns the expiration time
834 returns -EAGAIN or -EBUSY, and if the next autosuspend delay expiration time is
|
| /linux-4.1.27/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.1.27/include/net/sctp/ |
| D | structs.h | 286 ktime_t expiration; member
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-devices-power | 198 1000 will cause the autosuspend timer expiration to be rounded
|
| /linux-4.1.27/Documentation/usb/ |
| D | power-management.txt | 451 busy and therefore the next autosuspend idle-delay expiration should
|
| /linux-4.1.27/net/netfilter/ |
| D | Kconfig | 734 The remaining time for expiration can be read via sysfs.
|