Home
last modified time | relevance | path

Searched full:persistent (Results 1 – 25 of 483) sorted by relevance

12345678910>>...20

/Linux-v5.15/security/keys/
Dpersistent.c2 /* 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 …]
/Linux-v5.15/drivers/nvdimm/
DKconfig12 bus is registered to advertise PMEM (persistent memory)
23 tristate "PMEM: Persistent memory block device support"
35 these persistent memory ranges into block devices that are
48 apertures to access persistent media.
66 update semantics for persistent memory devices, so that
80 bool "PFN: Map persistent (device) memory"
85 Map persistent memory, i.e. advertise it to the memory
86 management sub-system. By default persistent memory does
95 bool "NVDIMM DAX: Raw access to persistent memory"
99 Support raw device dax access to a persistent memory
[all …]
/Linux-v5.15/Documentation/devicetree/bindings/pmem/
Dpmem-region.txt1 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-v5.15/tools/perf/pmu-events/arch/x86/cascadelakex/
Duncore-memory.json68 …": "Write requests allocated in the PMM Write Pending Queue for Intel Optane DC persistent memory",
76 …": "Write requests allocated in the PMM Write Pending Queue for Intel Optane DC persistent memory",
84 …"BriefDescription": "Intel Optane DC persistent memory bandwidth read (MB/sec). Derived from unc_m…
93 …"BriefDescription": "Intel Optane DC persistent memory bandwidth write (MB/sec). Derived from unc_…
102 …"BriefDescription": "Intel Optane DC persistent memory bandwidth total (MB/sec). Derived from unc_…
113 …iption": "Read Pending Queue Occupancy of all read requests for Intel Optane DC persistent memory",
122 …"BriefDescription": "Intel Optane DC persistent memory read latency (ns). Derived from unc_m_pmm_r…
184 "BriefDescription": "All commands for Intel Optane DC persistent memory",
189 "PublicDescription": "All commands for Intel Optane DC persistent memory",
194 "BriefDescription": "Regular reads(RPQ) commands for Intel Optane DC persistent memory",
[all …]
/Linux-v5.15/Documentation/admin-guide/mm/
Dhugetlbpage.rst30 persistent hugetlb pages in the kernel's huge page pool. It also displays
81 ``/proc/sys/vm/nr_hugepages`` indicates the current number of "persistent" huge
82 pages in the kernel's huge page pool. "Persistent" huge pages will be
84 privileges can dynamically allocate more or free some persistent huge pages
100 The administrator can allocate persistent huge pages on the kernel boot
163 default sized persistent huge pages::
175 silently skipped when allocating persistent huge pages. See the
178 with the allocation and freeing of persistent huge pages.
201 persistent huge page pool is exhausted. As these surplus huge pages become
205 surplus pages will first be promoted to persistent huge pages. Then, additional
[all …]
/Linux-v5.15/drivers/target/
Dtarget_core_pr.c5 * 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()
1241 * e) If the I_T nexus is the persistent reservation holder in core_scsi3_check_implicit_release()
1242 * and the persistent reservation is not an all registrants in core_scsi3_check_implicit_release()
[all …]
/Linux-v5.15/drivers/dax/
DKconfig25 tristate "PMEM DAX: direct access to persistent memory"
29 Support raw access to persistent memory. Note that this
57 tristate "KMEM DAX: volatile-use of persistent memory"
62 Support access to persistent, or other performance
64 easier use of persistent memory by unmodified applications, or
/Linux-v5.15/drivers/cxl/
DKconfig21 "System RAM" and/or "Persistent Memory" that is fully coherent
61 hierarchy to map regions that represent System RAM, or Persistent
67 tristate "CXL PMEM: Persistent Memory Support"
72 support for persistent memory attached via CXL. This support is
75 provisioning the persistent memory capacity of CXL memory expanders.
/Linux-v5.15/Documentation/ABI/testing/
Dpstore5 Description: Generic interface to platform dependent persistent storage.
27 the file will signal to the underlying persistent storage
33 will be saved elsewhere and erased from persistent store
40 persistent storage until at least this amount is reached.
/Linux-v5.15/Documentation/admin-guide/device-mapper/
Dsnapshot.rst34 - 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
Dwritecache.rst5 The writecache target caches writes on persistent memory or on SSD. It
15 - p - persistent memory
44 applicable only to persistent memory - use the FUA flag
45 when writing data from persistent memory back to the
48 applicable only to persistent memory - don't use the FUA
Dpersistent-data.rst2 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-v5.15/drivers/scsi/
Dconstants.c71 /* 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-v5.15/Documentation/block/
Dpr.rst2 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-v5.15/include/uapi/linux/
Dip_vs.h21 #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-v5.15/fs/pstore/
DKconfig3 tristate "Persistent store support"
8 persistent storage via "pstore" filesystem that can
12 (or "M") to a platform specific persistent store driver
14 If you don't have a platform persistent store driver,
137 bool "Persistent function tracer"
142 With this option kernel traces function calls into a persistent
/Linux-v5.15/arch/powerpc/platforms/pseries/
Dpmem.c4 * Handles hot and cold plug of persistent memory regions on pseries.
113 pmem_node = of_find_node_by_type(NULL, "ibm,persistent-memory"); in dlpar_hp_pmem()
143 { .type = "ibm,persistent-memory", },
155 pmem_node = of_find_node_by_type(NULL, "ibm,persistent-memory"); in pseries_pmem_init()
/Linux-v5.15/drivers/md/
Ddm-exception-store.c199 char persistent; in dm_exception_store_create() local
212 persistent = toupper(*argv[0]); in dm_exception_store_create()
213 if (persistent == 'P') in dm_exception_store_create()
215 else if (persistent == 'N') in dm_exception_store_create()
274 DMERR("Unable to register persistent exception store type"); in dm_exception_store_init()
/Linux-v5.15/fs/nilfs2/
Dalloc.h3 * alloc.h - persistent object (dat entry/disk inode) allocator/deallocator
40 * nilfs_palloc_req - persistent allocator request and reply
79 * struct nilfs_palloc_cache - persistent object allocator cache
/Linux-v5.15/tools/testing/selftests/powerpc/tm/
Dtm.h41 * 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-v5.15/Documentation/filesystems/
Ddax.rst47 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
195 - pmem: NVDIMM persistent memory driver
/Linux-v5.15/drivers/md/persistent-data/
DMakefile2 obj-$(CONFIG_DM_PERSISTENT_DATA) += dm-persistent-data.o
3 dm-persistent-data-objs := \
/Linux-v5.15/drivers/gpio/
Dgpio-arizona.c31 bool persistent = gpiochip_line_is_persistent(chip, offset); in arizona_gpio_direction_in() local
42 if (change && persistent) { in arizona_gpio_direction_in()
101 bool persistent = gpiochip_line_is_persistent(chip, offset); in arizona_gpio_direction_out() local
109 if ((val & ARIZONA_GPN_DIR) && persistent) { in arizona_gpio_direction_out()
/Linux-v5.15/Documentation/driver-api/nvdimm/
Dfirmware-activate.rst7 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-v5.15/tools/perf/scripts/python/
Dmem-phys-addr.py21 #physical address ranges for Persistent Memory
38 if m[2].strip() == 'Persistent Memory':
82 return "Persistent Memory"

12345678910>>...20