objects (full) in projects: Documentation

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:objects (Results 1 – 25 of 259) sorted by relevance

12 3 4 5 6 7 8 9 10 11

/Documentation/dev-tools/
D	kmemleak.rst	7 with the difference that the orphan objects are not freed but only 17 number of new unreferenced objects found. If the ``debugfs`` isn't already 37 Note that the orphan objects are listed in the order they were allocated 39 objects to be reported as orphan. 61 marking all current reported unreferenced objects grey, 62 or free all kmemleak objects if kmemleak has been disabled. 99 1. mark all objects as white (remaining white objects will later be 105 3. scan the gray objects for matching addresses (some white objects 108 4. the remaining white objects are considered orphan and reported via 123 'clear' command to clear all reported unreferenced objects from the [all …]
/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/
D	overview.rst	26 network ports to create functional objects/devices such as network 29 which DPAA2 software drivers use to operate on DPAA2 objects. 53 \| Resources Objects \| 71 DPIO objects. 73 Overview of DPAA2 Objects 76 The section provides a brief overview of some key DPAA2 objects. 77 A simple scenario is described illustrating the objects involved 84 types of DPAA2 objects. In the example diagram below there 85 are 8 objects of 5 types (DPMCP, DPIO, DPBP, DPNI, and DPMAC) 105 of the DPRC, discover the hardware objects present (including mappable [all …]
/Documentation/core-api/
D	debug-objects.rst	11 kernel objects and validate the operations on those. 15 - Activation of uninitialized objects 17 - Initialization of active objects 19 - Usage of freed/destroyed objects 62 tracking objects and the state of the internal tracking objects pool. 75 active and destroyed objects. When debugobjects detects an error, then 98 active and destroyed objects. When debugobjects detects an error, then 112 object returns. Otherwise we keep track of stale objects. 122 active and destroyed objects. When debugobjects detects an error, then 131 objects. The fixup function checks whether the object is valid and calls [all …]
D	assoc_array.rst	11 1. Objects are opaque pointers. The implementation does not care where they 16 Pointers to objects _must_ be zero in the least significant bit. 18 2. Objects do not need to contain linkage blocks for use by the array. This 20 Rather, the array is made up of metadata blocks that point to objects. 22 3. Objects require index keys to locate them within the array. 32 7. Index keys can include a hash to scatter objects throughout the array. 34 8. The array can iterated over. The objects will not necessarily come out in 39 circumstances, some objects may be seen more than once. If this is a 40 problem, the iterator should lock against modification. Objects will not 43 10. Objects in the array can be looked up by means of their index key. [all …]
/Documentation/admin-guide/mm/
D	shrinker_debugfs.rst	`48 3. Count objects 52 <cgroup inode id> <nr of objects on node 0> <nr of objects on node 1> ... 53 <cgroup inode id> <nr of objects on node 0> <nr of objects on node 1> ... 56 If there are no objects on all numa nodes, a line is omitted. If there 57 are no objects at all, the output might be empty. 106 4. Scan objects 110 <cgroup inode id> <numa id> <number of objects to scan>`
/Documentation/driver-api/acpi/
D	scan_handlers.rst	13 is scanned in search of device objects that generally represent various pieces 16 and the hierarchy of those struct acpi_device objects reflects the namespace 17 layout (i.e. parent device objects in the namespace are represented by parent 18 struct acpi_device objects and analogously for their children). Those struct 19 acpi_device objects are referred to as "device nodes" in what follows, but they 20 should not be confused with struct device_node objects used by the Device Trees 21 parsing code (although their role is analogous to the role of those objects). 28 information from the device objects represented by them and populating them with 38 basis of the device node's hardware ID (HID). They are performed by objects
/Documentation/mm/
D	zsmalloc.rst	19 For simplicity, zsmalloc can only allocate objects of size up to PAGE_SIZE 79 the number of objects allocated 81 the number of objects allocated to the user 90 objects stored in the zspage. The inuse counter determines the zspage's 91 "fullness group" which is calculated as the ratio of the "inuse" objects to 92 the total number of objects the zspage can hold (objs_per_zspage). The 105 of objects that each zspage can store. 118 #100 instead of size class #96. Size class #100 is meant for objects of size 122 hold a total of 5 objects. If we need to store 13 objects of size 1568, we 126 objects of size 1568 bytes) and trace `calculate_zspage_chain_size()`, we [all …]
D	memory-model.rst	40 have entries in the `mem_map` array. The `struct page` objects 87 The `mem_section` objects are arranged in a two-dimensional array 97 `mem_section` objects and the number of rows is calculated to fit 115 `struct page` objects. A PFN is an index to that array and the 129 The virtually mapped memory map allows storing `struct page` objects 142 that the page objects for these address ranges are never marked online, 173 * p2pdma: Create `struct page` objects to allow peer devices in a
D	slub.rst	126 in order to reduce overhead and increase cache hotness of objects. 138 which will test all objects. Output will be generated to the syslog. 141 In that case ``slabinfo -v`` simply tests all reachable objects. Usually 158 allows to specify how many objects must at least fit into one 303 keep corrupting objects. This may be important for production systems. 318 of other objects:: 400 allocated objects. The output is sorted by frequency of each trace. 403 Number of objects, allocating function, possible memory wastage of 404 kmalloc objects(total/per-object), minimal/average/maximal jiffies 431 objects. The freeing traces thus come from the previous life-cycle of the [all …]
/Documentation/networking/devlink/
D	netdevsim.rst	60 Rate objects 63 The ``netdevsim`` driver supports rate objects management, which includes: 65 - registerging/unregistering leaf rate objects per VF devlink port; 66 - creation/deletion node rate objects; 78 Same parameters are exposed for leaf objects in corresponding ports directories.
/Documentation/ABI/testing/
D	sysfs-kernel-slab	48 The alloc_fastpath file shows how many objects have been 72 was empty but there were objects available as the result of 93 The alloc_slowpath file shows how many objects have been 105 The cache_dma file is read-only and specifies whether objects 168 has been deactivated and contained free objects that were freed 201 slabs (not objects) are freed by rcu. 230 The free_fastpath file shows how many objects have been freed 241 The free_frozen file shows how many objects have been freed to 275 The free_slowpath file shows how many objects have been freed 287 objects are aligned on cachelines. [all …]
/Documentation/gpu/
D	drm-mm.rst	96 GEM is data-agnostic. It manages abstract buffer objects without knowing 134 GEM Objects Creation 137 GEM splits creation of GEM objects and allocation of the memory that 140 GEM objects are represented by an instance of struct :c:type:`struct 142 extend GEM objects with private information and thus create a 169 often the case in embedded devices. Drivers can create GEM objects with 170 no shmfs backing (called private GEM objects) by initializing them with a call 172 private GEM objects must be managed by drivers. 174 GEM Objects Lifetime 177 All GEM objects are reference-counted by the GEM core. References can be [all …]
D	drm-vm-bind-locking.rst	54 order. Please refer to the ``Reservation Objects`` section of the 64 single VM. Local GEM objects share the gpu_vm's dma_resv. 72 One of the benefits of VM_BIND is that local GEM objects share the gpu_vm's 74 number of local GEM objects, only one lock is needed to make the exec 98 GEM objects. 100 external GEM objects. 150 Revalidation and eviction of local objects 159 With VM_BIND, all local objects need to be resident when the gpu is 160 executing using the gpu_vm, and the objects need to have valid 174 // gpu_vmas, but since local gem objects share the gpu_vm's [all …]
/Documentation/admin-guide/sysctl/
D	user.rst	`15 limits on the number of namespaces and other objects that have 19 malfunction and attempt to create a ridiculous number of objects, 24 The creation of per user per user namespace objects are charged to 28 The creation of objects is also charged to all of the users 33 This recursive counting of created objects ensures that creating a`
/Documentation/iio/
D	iio_dmabuf_api.rst	`15 can attach DMABUF objects (externally created) to an IIO buffer, and 19 objects between several interfaces, allowing it to transfer data in a 22 The userspace application can also memory-map the DMABUF objects, and 49 automatically detach all previously attached DMABUF objects.`
/Documentation/admin-guide/blockdev/drbd/
D	data-structure-v9.rst	`15 The DRBD objects are interconnected to form a matrix as depicted below; a 32 their volume number. Objects in the vertical direction are connected by double 39 The drbd_resource, drbd_connection, and drbd_device objects are reference 40 counted. The peer_device objects only serve to establish the links between`
/Documentation/filesystems/caching/
D	cachefiles.rst	57 the filesystem, shrinking the cache by culling the objects it contains to make 158 Renaming files in the cache might make objects appear to be other objects (the 175 discarding objects from the cache that have been used less recently than 176 anything else. Culling is based on the access time of data objects. Empty 205 The userspace daemon scans the cache to build up a table of cullable objects. 207 started as soon as space is made in the table. Objects will be skipped if 220 The active cache objects all reside in the first directory. The CacheFiles 221 kernel module moves any retired or culled objects that it can't simply unlink 228 The module represents index objects as directories with the filename "I..." or 231 Data objects are represented as files if they have no children, or directories [all …]
D	backend-api.rst	42 Caches are represented in the API by cache cookies. These are objects of 106 The cache must then go through the data storage objects it has and tell fscache 136 Within a cache, the data storage objects are organised into logical volumes. 137 These are represented in the API as objects of type:: 174 A volume is a logical group of data storage objects, each of which is 176 the API as objects of type:: 248 completion until all objects have been destroyed. The following functions are 260 fscache to finish withdrawing all the objects in the cache. When it completes, 261 there will be no remaining objects referring to the cache object or any volume 262 objects. [all …]
/Documentation/userspace-api/
D	iommufd.rst	`30 User Visible Objects 33 Following IOMMUFD objects are exposed to userspace: 50 All user-visible objects are destroyed via the IOMMU_DESTROY uAPI. 52 The diagram below shows relationship between user-visible objects and kernel 54 creating the objects and links:: 86 hold multiple IOAS objects. IOAS is the most generic object and does not 119 User visible objects are backed by following datastructures:`
D	lsm.rst	`31 creating file system objects. 36 creating key objects. 47 creating socket objects.`
/Documentation/driver-api/pm/
D	cpuidle.rst	85 struct cpuidle_state objects representing idle states that the 118 :c:member:`states` array of struct cpuidle_state objects held by the 165 of struct cpuidle_state objects included in the struct cpuidle_driver object 243 However, it also is necessary to register struct cpuidle_device objects for 249 of registering the struct cpuidle_device objects as needed, so it is generally 258 ``CPUIdle`` drivers and struct cpuidle_device objects can be unregistered 261 struct cpuidle_device objects representing CPUs handled by the given 266 along with all of the struct cpuidle_device objects representing CPUs handled 275 all of the struct cpuidle_device objects representing CPUs affected by that 278 all of the relevant struct cpuidle_device objects and invoke
/Documentation/crypto/
D	intro.rst	`48 implementation. There can be multiple transformation objects associated 50 transformation objects is held by a crypto API consumer or another 55 The structure that contains transformation objects may also be referred`
/Documentation/RCU/
D	rculist_nulls.rst	`4 Using RCU hlist_nulls to protect list and objects 9 objects using SLAB_TYPESAFE_BY_RCU allocations. 19 Without 'nulls', a typical RCU linked list managing objects which are 22 objects, which is having below type. 41 if (!try_get_ref(obj)) { // might fail for free objects 169 if (!try_get_ref(obj)) { // might fail for free objects`
/Documentation/gpu/rfc/
D	i915_vm_bind.rst	8 objects (BOs) or sections of a BOs at specified GPU virtual addresses on a 31 * Support for userptr gem objects (no special uapi is required for this). 77 VM_PRIVATE objects 128 find the backing storage (dma_resv lock for gem objects, and hmm/core mm for 135 We need to ensure VM_BIND mapped objects are properly LRU tagged to avoid 137 VM_BIND objects to avoid additional latencies in execbuf path. 139 The page table pages are similar to VM_BIND mapped objects (See 146 Fences needs to be added to all VM_BIND mapped objects. During each execbuf 231 mapped objects. Page table pages are similar to persistent mappings of a
/Documentation/bpf/libbpf/
D	libbpf_naming_convention.rst	`25 Objects section in API naming convention 28 Another class of types and functions provided by libbpf API is "objects" 29 and functions to work with them. Objects are high-level abstractions 37 These objects are associated with corresponding parts of ELF object that 52 All objects and corresponding functions other than BTF related should go`

12 3 4 5 6 7 8 9 10 11

Documentation
LICENSES
arch
block
certs
crypto
drivers
fs
gki
include
init
io_uring
ipc
kernel
lib
mm
net
rust
samples
scripts
security
sound
tools
usr
virt