| /linux/security/keys/ |
| H A D | persistent.c | 2 /* General persistent per-UID keyrings register
16 * Create the persistent keyring register for the current user namespace.
36 * Create the persistent keyring for the specified user.
43 struct key *persistent; in key_create_persistent() local
57 persistent = keyring_alloc(index_key->description, in key_create_persistent()
63 if (IS_ERR(persistent)) in key_create_persistent()
64 return ERR_CAST(persistent); in key_create_persistent()
66 return make_key_ref(persistent, true); in key_create_persistent()
70 * Get the persistent keyring for a specific UID and link it to the nominated
77 struct key *persistent; in key_get_persistent() local
[all …]
|
| H A D | Kconfig | 43 bool "Enable register of persistent per-UID keyrings"
46 This option provides a register of persistent per-UID keyrings,
47 primarily aimed at Kerberos key storage. The keyrings are persistent
|
| /linux/drivers/nvdimm/ |
| H A D | Kconfig | 12 bus is registered to advertise PMEM (persistent memory)
20 tristate "PMEM: Persistent memory block device support"
32 these persistent memory ranges into block devices that are
50 update semantics for persistent memory devices, so that
63 bool "PFN: Map persistent (device) memory"
68 Map persistent memory, i.e. advertise it to the memory
69 management sub-system. By default persistent memory does
78 bool "NVDIMM DAX: Raw access to persistent memory"
82 Support raw device dax access to a persistent memory
84 persistent memory, this capability provides a mechanism to
[all …]
|
| /linux/Documentation/devicetree/bindings/pmem/ |
| H A D | pmem-region.txt | 1 Device-tree bindings for persistent memory regions
4 Persistent memory refers to a class of memory devices that are:
9 Given b) it is best to think of persistent memory as a kind of memory mapped
11 persistent regions separately to the normal memory pool. To aid with that this
12 binding provides a standardised interface for discovering where persistent
36 backed by non-persistent memory. This lets the OS know that it
38 persistent after a write.
|
| /linux/drivers/target/ |
| H A D | target_core_pr.c | 5 * This file contains SPC-3 compliant persistent reservations and
136 * persistent reservation shall not be changed, if the command in target_check_scsi2_reservation_conflict()
140 * status, but the persistent reservation shall not be released, in target_check_scsi2_reservation_conflict()
143 * a) An I_T nexus that is a persistent reservation holder; or in target_check_scsi2_reservation_conflict()
145 * all registrants type persistent reservation is present. in target_check_scsi2_reservation_conflict()
168 * If a logical unit has executed a PERSISTENT RESERVE OUT in target_check_scsi2_reservation_conflict()
306 * Begin SPC-3/SPC-4 Persistent Reservations emulation support
343 * Some commands are only allowed for the persistent reservation in core_scsi3_pr_seq_non_holder()
1240 * e) If the I_T nexus is the persistent reservation holder in core_scsi3_check_implicit_release()
1241 * and the persistent reservation is not an all registrants in core_scsi3_check_implicit_release()
[all …]
|
| /linux/drivers/cxl/ |
| H A D | Kconfig | 27 this class code provide support for volatile and / or persistent
71 hierarchy to map regions that represent System RAM, or Persistent
77 tristate "CXL PMEM: Persistent Memory Support"
82 support for persistent memory attached via CXL. This support is
85 provisioning the persistent memory capacity of CXL memory expanders.
95 RAM" and/or "Persistent Memory" that is fully coherent as if the
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | snapshot.rst | 34 - snapshot <origin> <COW device> <persistent?> <chunksize>
45 <persistent?> is P (Persistent) or N (Not persistent - will not survive
46 after reboot). O (Overflow) can be added as a persistent store option
50 The difference between persistent and transient is with transient
73 - snapshot-merge <origin> <COW device> <persistent> <chunksize>
77 works with persistent snapshots. This target assumes the role of the
|
| H A D | writecache.rst | 5 The writecache target caches writes on persistent memory or on SSD. It
15 - p - persistent memory
45 applicable only to persistent memory - use the FUA flag
46 when writing data from persistent memory back to the
49 applicable only to persistent memory - don't use the FUA
|
| H A D | persistent-data.rst | 2 Persistent data
20 The persistent-data library is an attempt to provide a re-usable
29 under drivers/md/persistent-data.
40 Clients of persistent-data are unlikely to use this directly.
|
| /linux/drivers/scsi/ |
| H A D | constants.c | 71 /* 5c-5f */ "Read buffer capacity", "Send cue sheet", "Persistent reserve in",
72 "Persistent reserve out",
160 {0x0, "Persistent reserve in, read keys"},
161 {0x1, "Persistent reserve in, read reservation"},
162 {0x2, "Persistent reserve in, report capabilities"},
163 {0x3, "Persistent reserve in, read full status"},
168 {0x0, "Persistent reserve out, register"},
169 {0x1, "Persistent reserve out, reserve"},
170 {0x2, "Persistent reserve out, release"},
171 {0x3, "Persistent reserve out, clear"},
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | pstore | 6 Description: Generic interface to platform dependent persistent storage.
28 the file will signal to the underlying persistent storage
34 will be saved elsewhere and erased from persistent store
41 persistent storage until at least this amount is reached.
|
| /linux/fs/pstore/ |
| H A D | Kconfig | 3 tristate "Persistent store support"
7 persistent storage via "pstore" filesystem that can
11 (or "M") to a platform specific persistent store driver
13 If you don't have a platform persistent store driver,
56 bool "Persistent function tracer"
61 With this option kernel traces function calls into a persistent
|
| /linux/Documentation/filesystems/ |
| H A D | dax.rst | 47 2. There exists a persistent flag `FS_XFLAG_DAX` that can be applied to regular
51 3. If the persistent `FS_XFLAG_DAX` flag is set on a directory, this flag will
92 6. When changing the `S_DAX` policy via toggling the persistent `FS_XFLAG_DAX`
100 There are 2 per-file dax flags. One is a persistent inode setting (`FS_XFLAG_DAX`)
104 `FS_XFLAG_DAX` is preserved within the filesystem. This persistent config
176 rather than the persistent `FS_XFLAG_DAX` flag. That is, whether DAX shall be
179 on the persistent `FS_XFLAG_DAX` flag on the host.
181 It is still supported to set or clear persistent `FS_XFLAG_DAX` flag inside
211 - pmem: NVDIMM persistent memory driver
|
| /linux/include/uapi/linux/ |
| H A D | ip_vs.h | 21 #define IP_VS_SVC_F_PERSISTENT 0x0001 /* persistent port */
154 unsigned int timeout; /* persistent timeout in sec */
155 __be32 netmask; /* persistent netmask */
216 unsigned int timeout; /* persistent timeout */
217 __be32 netmask; /* persistent netmask */
238 __u32 persistconns; /* persistent connections */
368 IPVS_SVC_ATTR_TIMEOUT, /* persistent timeout */
369 IPVS_SVC_ATTR_NETMASK, /* persistent netmask */
400 IPVS_DEST_ATTR_PERSIST_CONNS, /* persistent connections */
|
| /linux/Documentation/block/ |
| H A D | pr.rst | 2 Block layer support for Persistent Reservations
6 Persistent Reservations which map to block devices that support
7 these (like SCSI). Persistent Reservations allow restricting
14 "PERSISTENT RESERVE IN" and "PERSISTENT RESERVE OUT" commands.
|
| /linux/drivers/dax/ |
| H A D | Kconfig | 20 tristate "PMEM DAX: direct access to persistent memory"
24 Support raw access to persistent memory. Note that this
70 Support access to persistent, or other performance
72 easier use of persistent memory by unmodified applications, or
|
| /linux/Documentation/networking/ |
| H A D | net_failover.rst | 48 <teaming type='persistent'/>
56 <teaming type='transient' persistent='ua-backup0'/>
60 interface and this acts as the 'persistent' device indicating that this
62 required attribute type having value 'persistent'. The link state for the
69 periodically be unplugged. A second attribute - 'persistent' is provided and
133 <teaming type='transient' persistent='ua-backup0'/>
163 virsh migrate --live --persistent $DOMAIN qemu+ssh://$REMOTE_HOST/system
|
| /linux/arch/powerpc/platforms/pseries/ |
| H A D | pmem.c | 4 * Handles hot and cold plug of persistent memory regions on pseries.
112 pmem_node = of_find_node_by_type(NULL, "ibm,persistent-memory"); in dlpar_hp_pmem()
142 { .type = "ibm,persistent-memory", },
154 pmem_node = of_find_node_by_type(NULL, "ibm,persistent-memory"); in pseries_pmem_init()
|
| /linux/drivers/md/dm-vdo/indexer/ |
| H A D | geometry.c | 28 * The index volume is sized by its maximum memory footprint. For a dense index, the persistent
29 * storage is about 10 times the size of the memory footprint. For a sparse index, the persistent
37 * GB for the persistent storage and 256 MB of RAM.
42 * of 1 TB using about 9GB of persistent storage and 1 GB of RAM.
46 * deduplication window while using 10 times as much persistent storage as the equivalent
|
| /linux/drivers/md/ |
| H A D | dm-exception-store.c | 200 char persistent; in dm_exception_store_create() local
213 persistent = toupper(*argv[0]); in dm_exception_store_create()
214 if (persistent == 'P') in dm_exception_store_create()
216 else if (persistent == 'N') in dm_exception_store_create()
275 DMERR("Unable to register persistent exception store type"); in dm_exception_store_init()
|
| /linux/tools/testing/selftests/powerpc/tm/ |
| H A D | tm.h | 41 * Bit 7 (Failure Persistent) and Bit 15 (Implementation-specific).
48 * Per the ISA, the Failure Persistent bit may be incorrect. Try a few in htm_is_synthetic()
51 * should not be persistent. in htm_is_synthetic()
|
| /linux/drivers/gpio/ |
| H A D | gpio-arizona.c | 30 bool persistent = gpiochip_line_is_persistent(chip, offset); in arizona_gpio_direction_in() local
41 if (change && persistent) { in arizona_gpio_direction_in()
100 bool persistent = gpiochip_line_is_persistent(chip, offset); in arizona_gpio_direction_out() local
108 if ((val & ARIZONA_GPN_DIR) && persistent) { in arizona_gpio_direction_out()
|
| /linux/tools/perf/scripts/python/ |
| H A D | mem-phys-addr.py | |
| /linux/Documentation/driver-api/nvdimm/ |
| H A D | firmware-activate.rst | 7 Some persistent memory devices run a firmware locally on the device /
12 persistent memory platform implementation, described by the Intel ACPI
86 [1]: https://docs.pmem.io/persistent-memory/
|
| /linux/drivers/md/persistent-data/ |
| H A D | Makefile | 2 obj-$(CONFIG_DM_PERSISTENT_DATA) += dm-persistent-data.o
3 dm-persistent-data-objs := \
|