Home
last modified time | relevance | path

Searched refs:objects (Results 1 – 195 of 195) sorted by relevance

/linux-4.4.14/drivers/staging/fsl-mc/
DREADME.txt11 -Overview of DPAA2 objects
34 network ports to create functional objects/devices such as network
38 which DPAA2 software drivers use to operate on DPAA2 objects:
76 DPIO objects.
80 The section provides a brief overview of some key objects
82 the objects involved in creating a network interfaces.
87 types of DPAA2 objects. In the example diagram below there
88 are 8 objects of 5 types (DPMCP, DPIO, DPBP, DPNI, and DPMAC)
107 objects present (including mappable regions and interrupts).
117 Hardware objects can be created and destroyed dynamically, providing
[all …]
DTODO6 driver support, which depends on drivers for several objects: DPNI,
/linux-4.4.14/drivers/gpu/drm/radeon/
Dradeon_mn.c53 struct rb_root objects; member
78 rbtree_postorder_for_each_entry_safe(node, next_node, &rmn->objects, in radeon_mn_destroy()
81 interval_tree_remove(&node->it, &rmn->objects); in radeon_mn_destroy()
134 it = interval_tree_iter_first(&rmn->objects, start, end); in radeon_mn_invalidate_range_start()
206 rmn->objects = RB_ROOT; in radeon_mn_get()
254 while ((it = interval_tree_iter_first(&rmn->objects, addr, end))) { in radeon_mn_register()
257 interval_tree_remove(&node->it, &rmn->objects); in radeon_mn_register()
279 interval_tree_insert(&node->it, &rmn->objects); in radeon_mn_register()
316 interval_tree_remove(&node->it, &rmn->objects); in radeon_mn_unregister()
Dradeon_prime.c77 list_add_tail(&bo->list, &rdev->gem.objects); in radeon_gem_prime_import_sg_table()
Dradeon_gem.c87 list_add_tail(&robj->list, &rdev->gem.objects); in radeon_gem_object_create()
128 INIT_LIST_HEAD(&rdev->gem.objects); in radeon_gem_init()
777 list_for_each_entry(rbo, &rdev->gem.objects, list) { in radeon_debugfs_gem_info()
Dradeon_object.c431 if (list_empty(&rdev->gem.objects)) { in radeon_bo_force_delete()
435 list_for_each_entry_safe(bo, n, &rdev->gem.objects, list) { in radeon_bo_force_delete()
Dradeon_pm.c148 if (list_empty(&rdev->gem.objects)) in radeon_unmap_vram_bos()
151 list_for_each_entry_safe(bo, n, &rdev->gem.objects, list) { in radeon_unmap_vram_bos()
Dradeon.h569 struct list_head objects; member
/linux-4.4.14/drivers/gpu/drm/amd/amdgpu/
Damdgpu_mn.c53 struct rb_root objects; member
78 rbtree_postorder_for_each_entry_safe(node, next_node, &rmn->objects, in amdgpu_mn_destroy()
81 interval_tree_remove(&node->it, &rmn->objects); in amdgpu_mn_destroy()
134 it = interval_tree_iter_first(&rmn->objects, start, end); in amdgpu_mn_invalidate_range_start()
207 rmn->objects = RB_ROOT; in amdgpu_mn_get()
255 while ((it = interval_tree_iter_first(&rmn->objects, addr, end))) { in amdgpu_mn_register()
258 interval_tree_remove(&node->it, &rmn->objects); in amdgpu_mn_register()
280 interval_tree_insert(&node->it, &rmn->objects); in amdgpu_mn_register()
317 interval_tree_remove(&node->it, &rmn->objects); in amdgpu_mn_unregister()
Damdgpu_prime.c77 list_add_tail(&bo->list, &adev->gem.objects); in amdgpu_gem_prime_import_sg_table()
Damdgpu_gem.c89 list_add_tail(&robj->list, &adev->gem.objects); in amdgpu_gem_object_create()
97 INIT_LIST_HEAD(&adev->gem.objects); in amdgpu_gem_init()
703 list_for_each_entry(rbo, &adev->gem.objects, list) { in amdgpu_debugfs_gem_info()
Damdgpu_object.c477 if (list_empty(&adev->gem.objects)) { in amdgpu_bo_force_delete()
481 list_for_each_entry_safe(bo, n, &adev->gem.objects, list) { in amdgpu_bo_force_delete()
Damdgpu.h622 struct list_head objects; member
/linux-4.4.14/Documentation/filesystems/caching/
Dfscache.txt103 (5) Cookies are used to represent indices, files and other objects to the
130 FS-Cache maintains a virtual indexing tree in which all indices, files, objects
164 indexed by NFS file handles to get data file objects. Each data file
165 objects can have an array of pages, but may also have further child
166 objects, such as extended attributes and directory entries. Extended
167 attribute objects themselves have page-array contents.
172 Each of these contains vnode data file objects, each of which contains an
218 Objects alc=N Number of objects allocated
220 avl=N Number of objects that reached the available state
221 ded=N Number of objects that reached the dead state
[all …]
Dobject.txt26 currently interested in. Such objects are represented by the fscache_cookie
29 FS-Cache also maintains a separate in-kernel representation of the objects that
30 a cache backend is currently actively caching. Such objects are represented by
33 as objects.
35 There is a 1:N relationship between cookies and objects. A cookie may be
36 represented by multiple objects - an index may exist in more than one cache -
37 or even by no objects (it may not be cached).
39 Furthermore, both cookies and objects are hierarchical. The two hierarchies
83 and DObject represent data storage objects. Indices may have representation in
84 multiple caches, but currently, non-index objects may not. Objects of any type
[all …]
Dcachefiles.txt54 the filesystem, shrinking the cache by culling the objects it contains to make
169 Renaming files in the cache might make objects appear to be other objects (the
187 discarding objects from the cache that have been used less recently than
188 anything else. Culling is based on the access time of data objects. Empty
223 The userspace daemon scans the cache to build up a table of cullable objects.
240 The active cache objects all reside in the first directory. The CacheFiles
241 kernel module moves any retired or culled objects that it can't simply unlink
248 The module represents index objects as directories with the filename "I..." or
251 Data objects are represented as files if they have no children, or directories
253 directory, data objects will have a file in the directory called "data" that
[all …]
Dnetfs-api.txt10 FS-Cache to make finding objects faster and to make retiring of groups of
11 objects easier.
105 (1) Any index containing non-index objects should be restricted to a single
106 cache. Any such objects created within an index will be created in the
228 If this function is absent, it will be assumed that matching objects in a
415 Miscellaneous objects might be used to store extended attributes or directory
759 invalidates any backing objects and waits for cessation of activity on any
774 cookie, will begin the procedure of acquiring backing objects.
780 as enabled if provisional backing objects are allocated.
832 Not only that but all child objects will also be retired.
[all …]
Dbackend-api.txt635 all the objects.
/linux-4.4.14/Documentation/
Dkmemleak.txt10 with the difference that the orphan objects are not freed but only
21 number of new unreferenced objects found. To display the details of all
38 Note that the orphan objects are listed in the order they were allocated
40 objects to be reported as orphan.
54 marking all current reported unreferenced objects grey,
55 or free all kmemleak objects if kmemleak has been disabled.
87 1. mark all objects as white (remaining white objects will later be
93 3. scan the gray objects for matching addresses (some white objects
96 4. the remaining white objects are considered orphan and reported via
111 'clear' command to clear all reported unreferenced objects from the
[all …]
Dassoc_array.txt34 [!] NOTE: Pointers to objects _must_ be zero in the least significant bit.
38 Rather, the array is made up of metadata blocks that point to objects.
50 (7) Index keys can include a hash to scatter objects throughout the array.
52 (8) The array can iterated over. The objects will not necessarily come out in
57 circumstances, some objects may be seen more than once. If this is a
97 This is also used to keep track of dead blocks and dead objects after the
165 (4) Diff the index keys of two objects.
240 (4) Delete all objects from an associative array.
246 This deletes all the objects from an associative array and leaves it
256 (5) Destroy an associative array, deleting all objects.
[all …]
Dkobject.txt21 objects to be arranged into hierarchies), a specific type, and,
58 nice to have in other objects. The C language does not allow for the
64 their own, but are invariably found embedded in the larger objects of
301 and default_attrs) control how objects of this type are represented in
316 - It serves as a bag containing a group of objects. A kset can be used by
406 parent objects references a child. Circular references _must_ be broken
408 called, and the objects in the former circle release each other.
Dflexible-arrays.txt20 objects, accessed via an integer index. Sparse arrays are handled
38 maximum number of objects which can be stored in the array. The flags
Dkref.txt2 krefs allow you to add reference counters to your objects. If you
3 have objects that are used in multiple places and passed around, and
Dpi-futex.txt50 So once we accept that synchronization objects (locks) are an
Dkasan.txt64 INFO: Slab 0xffffea0001a4ef00 objects=17 used=7 fp=0xffff8800693bd728 flags=0x100000000004080
Dcircular-buffers.txt15 (2) Memory barriers for when the producer and the consumer of objects in the
D00-INDEX277 - docs on adding reference counters (krefs) to kernel objects.
453 - directory with info regarding virtual dynamic shared objects
Dintel_txt.txt64 boot as well as data objects used by that code. In the case of a
Dmemory-hotplug.txt216 calls hotplug code for all of objects which are defined in it.
Dkernel-parameters.txt199 the return objects more ACPI specification compliant.
271 named objects will be marked as "Serialized" by the
3511 culprit if slab objects become corrupted. Enabling
3512 slub_debug can create guard zones around objects and
3513 may poison objects when not in use. Also tracks the
3524 The minimum number of objects per slab. SLUB will
3527 the number of objects indicated. The higher the number
3528 of objects the smaller the overhead of tracking slabs
DCodingStyle290 (a) totally opaque objects (where the typedef is actively used to _hide_
293 Example: "pte_t" etc. opaque objects that you can only access using
Ddma-buf-sharing.txt276 To support dma_buf objects residing in highmem cpu access is page-based using
Datomic_ops.txt427 Native atomic bit operations are defined to operate on objects aligned
Dkmemcheck.txt599 we found earlier when looking for where siginfo_t objects are enqueued on the
Dkprobes.txt128 pre-allocates the indicated number of kretprobe_instance objects.
DDMA-API-HOWTO.txt952 objects).
DSubmittingPatches182 SHA-1 ID. The kernel repository holds a *lot* of objects, making
Dmemory-barriers.txt1710 example, when the objects removed only when the system goes down.
/linux-4.4.14/scripts/kconfig/
Dstreamline_config.pl146 my %objects;
335 if (defined($objects{$1})) {
336 @arr = @{$objects{$1}};
343 $objects{$1} = \@arr;
398 if (defined($objects{$module})) {
399 my @arr = @{$objects{$module}};
634 if (defined($objects{$module})) {
635 my @arr = @{$objects{$module}};
Dzconf.tab.c_shipped411 /* Copy COUNT objects from SRC to DST. The source and destination do
/linux-4.4.14/tools/perf/Documentation/
DBuild.txt18 main makefile that triggers build of all perf objects including
28 makefiles that defines build objects
36 The Makefile.perf triggers the build framework for build objects:
39 resulting in following objects:
43 Those objects are then used in final linking:
Dexamples.txt70 Counting objects: 1148, done.
72 Compressing objects: 100% (450/450), done.
73 Writing objects: 100% (1148/1148), done.
124 Counting objects: 1148, done.
126 Compressing objects: 100% (450/450), done.
127 Writing objects: 100% (1148/1148), done.
/linux-4.4.14/Documentation/acpi/
Dscan_handlers.txt7 is scanned in search of device objects that generally represent various pieces
10 and the hierarchy of those struct acpi_device objects reflects the namespace
11 layout (i.e. parent device objects in the namespace are represented by parent
12 struct acpi_device objects and analogously for their children). Those struct
13 acpi_device objects are referred to as "device nodes" in what follows, but they
14 should not be confused with struct device_node objects used by the Device Trees
15 parsing code (although their role is analogous to the role of those objects).
22 information from the device objects represented by them and populating them with
32 basis of the device node's hardware ID (HID). They are performed by objects
Dnamespace.txt9 The Linux ACPI subsystem converts ACPI namespace objects into a Linux
36 blocks that contain definitions of various objects, including ACPI
80 is a hierarchy of objects identified by names and paths.
190 objects for ACPI namespace objects representing devices, power resources
191 processors, thermal zones. Those objects are exported to user space via
229 The following rules apply when creating struct acpi_device objects on
254 struct acpi_device objects represented by the given row (xSDT means DSDT
261 is derived from the _HID/_CID identification objects present under
267 objects having bus_id of the "LNXxxxxx" form (pseudo devices), in
280 ACPI device (i.e. struct acpi_device) objects may be linked to other
[all …]
Dgpio-properties.txt61 In those cases ACPI device identification objects, _HID, _CID, _CLS, _SUB, _HRV,
71 array of struct acpi_gpio_mapping objects that each contain a name, a pointer
72 to an array of line data (struct acpi_gpio_params) objects and the size of that
Dmethod-customizing.txt45 And remember to use "External" to declare external objects.
Denumeration.txt385 object be present for all ACPI objects representing devices (Section 6.1 of ACPI
413 It is valid to define device objects with a _HID returning PRP0001 and without
416 objects are then simply regarded as additional "blocks" providing hierarchical
/linux-4.4.14/tools/build/Documentation/
DBuild.txt5 idea and the way how objects are built is the same.
7 Basically the user provides set of 'Build' files that list objects and
11 we setup source objects, but we support more. This allows one 'Build' file to
12 carry a sources list for multiple build objects.
46 The user supplies 'Build' makefiles that contains a objects list, and connects
64 only prepares proper objects to be compiled and grouped together.
86 which creates the following objects:
91 that contain request objects names in Build files.
164 $ make util/map.o # objects
/linux-4.4.14/tools/vm/
Dslabinfo.c35 unsigned long partial, objects, slabs, objects_partial, objects_total; member
350 return slab_size(s) - s->objects * s->object_size; in slab_waste()
525 s->name, s->aliases, s->order, s->objects); in report()
542 onoff(s->red_zone), s->objects * s->object_size); in report()
545 s->slabs * (page_size << s->order) - s->objects * s->object_size); in report()
548 (s->slab_size - s->object_size) * s->objects); in report()
619 s->name, s->objects, in slabcache()
627 s->name, s->objects, s->object_size, size_str, dist_str, in slabcache()
630 s->slabs ? (s->objects * s->object_size * 100) / in slabcache()
690 if (s->objects > 0) in slab_empty()
[all …]
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-kernel-slab48 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 …]
Dsysfs-bus-acpi8 This file is not present for device objects representing
26 This file is present for device objects having the _HID
42 objects representing devices having standard enumeration
Dsysfs-devices-resource_in_use6 for device objects representing ACPI power resources.
Dsysfs-devices-power_resources_D06 present for device objects representing ACPI device nodes that
Dsysfs-devices-power_resources_wakeup6 present for device objects representing ACPI device nodes that
Dsysfs-devices-power_resources_D16 present for device objects representing ACPI device nodes that
Dsysfs-devices-power_resources_D26 present for device objects representing ACPI device nodes that
Dsysfs-devices-power_resources_D3hot6 present for device objects representing ACPI device nodes that
Dsysfs-ata7 retrieving various information about ATA objects.
27 topology, 15 ata_link objects are created.
Dsysfs-devices-power_state6 device objects representing ACPI device nodes that provide power
Dsysfs-devices-real_power_state6 for device objects representing ACPI device nodes that provide
Dsysfs-class-net-queues59 Indicates the number of bytes (objects) in flight on this
Dsysfs-class-extcon5 Provide a place in sysfs for the extcon objects.
Dsysfs-class-devfreq5 Provide a place in sysfs for the devfreq objects.
Dsysfs-block-zram150 allocator zrm uses. The allocator moves some objects so that
Dsysfs-power210 wakeup source objects and activate them on demand (if one of
Dsysfs-bus-iio1237 indicate closer objects, and vice versa.
/linux-4.4.14/Documentation/vm/
Dzsmalloc.txt18 For simplicity, zsmalloc can only allocate objects of size up to PAGE_SIZE
56 obj_allocated: the number of objects allocated
57 obj_used: the number of objects allocated to the user
63 n = number of allocated objects
64 N = total number of objects zspage can store
Dslub.txt81 not contain objects. If the slab already contains objects then sanity checks
83 of objects.
92 in order to reduce overhead and increase cache hotness of objects.
103 which will test all objects. Output will be generated to the syslog.
106 In that case slabinfo -v simply tests all reachable objects. Usually
122 slub_min_objects allows to specify how many objects must at least fit
264 keep corrupting objects. This may be important for production systems.
279 of other objects.
Dhwpoison.txt182 objects cannot be recovered, only LRU pages for now.
Dnuma_memory_policy.txt102 Shared Policy: Conceptually, shared policies apply to "memory objects"
/linux-4.4.14/fs/configfs/
DKconfig7 view of kernel objects, configfs is a filesystem-based manager
8 of kernel objects, or config_items.
/linux-4.4.14/Documentation/filesystems/
Ddirectory-locking5 When taking the i_mutex on multiple non-directory objects, we
52 objects - A < B iff A is an ancestor of B.
66 (3) locks on non-directory objects are acquired only after locks on
67 directory objects, and are acquired in inode pointer order.
81 non-directory objects are not included in the set of contended locks.
92 Otherwise the set of contended objects would be infinite - each of them
99 would again have an infinite set of contended objects). But that
110 source), such loop would have to contain these objects and the rest of it
125 children", so if we are going to introduce hybrid objects we will need
Dxfs-delayed-logging-design.txt7 XFS logging is a combination of logical and physical logging. Some objects,
10 structures. Other objects - typically buffers - have their physical changes
12 required for objects that are frequently logged. Some parts of inodes are more
42 This relogging technique also allows objects to be moved forward in the log so
62 the log - repeated operations to the same objects write the same changes to
63 the log over and over again. Worse is the fact that objects tend to get
91 relogging technique XFS uses is that we can be relogging changed objects
101 objects, these "stale objects" can be over 90% of the space used in the log
102 buffers. It is clear that reducing the number of stale objects written to the
111 accumulating stale objects in the log buffers.
[all …]
Doverlayfs.txt17 This approach is 'hybrid' because the objects that appear in the
24 all non-directory objects will report an st_dev from the lower or
62 Where both upper and lower objects are directories, a merged directory
Dexofs.txt10 array of sectors but as a container of objects, each having a length, quota,
132 possible to extend the file over multiple objects, though this has not been
Dlogfs.txt54 objects, each consisting of the object header and the payload.
69 Each segment contains objects of a single level only. As a result,
Dsysfs.txt2 sysfs - _The_ filesystem for exporting kernel objects.
39 ancestors of object hierarchies; i.e. the subsystems the objects
D00-INDEX139 - info on sysfs, a ram-based filesystem for exporting kernel objects.
Dxfs-self-describing-metadata.txt68 magic numbers. Hence we can change the on-disk format of all these objects to
70 numbers in the metadata objects. That is, if it has the current magic number,
330 self-identifiers, but they are packed so that there are multiple objects per
Dext2.txt33 grpid, bsdgroups Give objects the same group ID as their parent.
34 nogrpid, sysvgroups New objects have the group ID of their creator.
193 Symbolic links are also filesystem objects with inodes. They deserve
Dceph.txt26 utilize btrfs to store data objects, leveraging its advanced features
Dcoda.txt219 read/write and create and remove objects. The Coda FS layer services
288 synchronization objects. In the upcall routine the message structure
294 created, and implemented using available synchronization objects in
777 create. The VFS operation create is only called to create new objects.
1440 objects are called ccnnooddeess.
1457 invalidate cache entries when it modifies or removes objects.
1665 best implemented by Venus fetching these objects before attempting
Dseq_file.txt33 step through the objects it is presenting.
35 * Some utility functions for formatting objects for output without
Dqnx6.txt112 Symbolic links are also filesystem objects with inodes. They got a specific
Dpath-lookup.txt113 However, when the dentry's list pointers are updated to point to objects in the
324 very least because i_mutex needs to be grabbed, and objects allocated.
Dext4.txt236 grpid Give objects the same group ID as their creator.
239 nogrpid (*) New objects have the group ID of their creator.
Dvfs.txt50 filesystem objects such as regular files, directories, FIFOs and other
303 filesystem to return the number of freeable cached objects it contains.
307 filesystem to scan the number of objects indicated to try to free them.
Dsharedsubtree.txt197 namespaces are made first class objects with user API to
Dproc.txt754 Commonly used objects have their own slab pool (such as network buffers,
1735 pair provide additional information particular to the objects they represent.
/linux-4.4.14/mm/
Dslub.c237 if (object < base || object >= base + page->objects * s->size || in check_valid_pointer()
361 page->objects = tmp.objects; in set_page_slub_counters()
587 page, page->objects, page->inuse, page->freelist, page->flags); in print_page_info()
877 if (page->objects > maxobj) { in check_slab()
879 page->objects, maxobj); in check_slab()
882 if (page->inuse > page->objects) { in check_slab()
884 page->inuse, page->objects); in check_slab()
904 while (fp && nr <= page->objects) { in on_freelist()
915 page->inuse = page->objects; in on_freelist()
930 if (page->objects != max_objects) { in on_freelist()
[all …]
Dzsmalloc.c630 max_objects = page->objects; in get_fullness_group()
1003 first_page->objects = class->pages_per_zspage * PAGE_SIZE / class->size; in alloc_zspage()
1238 return page->inuse == page->objects; in zspage_full()
/linux-4.4.14/Documentation/blockdev/drbd/
Ddata-structure-v9.txt11 The DRBD objects are interconnected to form a matrix as depicted below; a
35 The drbd_resource, drbd_connection, and drbd_device objects are reference
36 counted. The peer_device objects only serve to establish the links between
/linux-4.4.14/drivers/acpi/acpica/
Devregion.c756 union acpi_object objects[2]; in acpi_ev_orphan_ec_reg_method() local
796 args.pointer = objects; in acpi_ev_orphan_ec_reg_method()
797 objects[0].type = ACPI_TYPE_INTEGER; in acpi_ev_orphan_ec_reg_method()
798 objects[0].integer.value = ACPI_ADR_SPACE_EC; in acpi_ev_orphan_ec_reg_method()
799 objects[1].type = ACPI_TYPE_INTEGER; in acpi_ev_orphan_ec_reg_method()
800 objects[1].integer.value = ACPI_REG_CONNECT; in acpi_ev_orphan_ec_reg_method()
Ddbexec.c84 void acpi_db_delete_objects(u32 count, union acpi_object *objects) in acpi_db_delete_objects() argument
89 switch (objects[i].type) { in acpi_db_delete_objects()
92 ACPI_FREE(objects[i].buffer.pointer); in acpi_db_delete_objects()
99 acpi_db_delete_objects(objects[i].package.count, in acpi_db_delete_objects()
100 objects[i].package.elements); in acpi_db_delete_objects()
104 ACPI_FREE(objects[i].package.elements); in acpi_db_delete_objects()
Dacdebug.h215 void acpi_db_delete_objects(u32 count, union acpi_object *objects);
Ddbnames.c719 info->objects++; in acpi_db_integrity_walk()
753 info.nodes, info.objects); in acpi_db_check_integrity()
Daclocal.h1136 u32 objects; member
/linux-4.4.14/drivers/gpu/drm/qxl/
Dqxl_gem.c69 list_add_tail(&qbo->list, &qdev->gem.objects); in qxl_gem_object_create()
116 INIT_LIST_HEAD(&qdev->gem.objects); in qxl_gem_init()
Dqxl_object.c271 if (list_empty(&qdev->gem.objects)) in qxl_bo_force_delete()
274 list_for_each_entry_safe(bo, n, &qdev->gem.objects, list) { in qxl_bo_force_delete()
Dqxl_debugfs.c60 list_for_each_entry(bo, &qdev->gem.objects, list) { in qxl_debugfs_buffers_info()
Dqxl_kms.c134 INIT_LIST_HEAD(&qdev->gem.objects); in qxl_device_init()
Dqxl_drv.h126 struct list_head objects; member
/linux-4.4.14/Documentation/devicetree/bindings/misc/
Dfsl,qoriq-mc.txt4 manager that manages specialized hardware objects used in
8 blocks that can be used to create functional hardware objects/devices
/linux-4.4.14/Documentation/locking/
Dww-mutex-design.txt43 Compared to normal mutexes two additional concepts/objects show up in the lock
109 This is useful if a list of required objects is already tracked somewhere.
209 Method 3 is useful if the list of objects is constructed ad-hoc and not upfront,
216 - Due to the -EALREADY return code signalling that a given objects is already
222 - Since the list of objects is dynamically constructed (and might very well be
231 methods. And then lock any additional objects affected by the operations using
234 objects acquired with the fixed list. But the w/w mutex debug checks will catch
269 /* magic code which walks over a graph and decides which objects
299 Method 4: Only lock one single objects. In that case deadlock detection and
Dlockdep-design.txt135 is some sort of hierarchy within objects of the same type. In these
136 cases there is an inherent "natural" ordering between the two objects
138 locks in this fixed order on each of the objects.
Dlglock.txt113 access all protected per_cpu objects on all CPUs
/linux-4.4.14/drivers/gpu/drm/i915/
Di915_gem_userptr.c51 struct rb_root objects; member
140 it = interval_tree_iter_first(&mn->objects, start, end); in i915_gem_userptr_mn_invalidate_range_start()
166 mn->objects = RB_ROOT; in i915_mmu_notifier_create()
202 it = interval_tree_iter_first(&mn->objects, in i915_mmu_notifier_add()
224 interval_tree_insert(&mo->it, &mn->objects); in i915_mmu_notifier_add()
255 interval_tree_remove(&mo->it, &mn->objects); in i915_mmu_notifier_del()
Di915_gem_execbuffer.c100 struct list_head objects; in eb_lookup_vmas() local
103 INIT_LIST_HEAD(&objects); in eb_lookup_vmas()
126 list_add_tail(&obj->obj_exec_link, &objects); in eb_lookup_vmas()
131 while (!list_empty(&objects)) { in eb_lookup_vmas()
134 obj = list_first_entry(&objects, in eb_lookup_vmas()
173 while (!list_empty(&objects)) { in eb_lookup_vmas()
174 obj = list_first_entry(&objects, in eb_lookup_vmas()
Di915_dma.c1125 kmem_cache_destroy(dev_priv->objects); in i915_driver_load()
1217 kmem_cache_destroy(dev_priv->objects); in i915_driver_unload()
Di915_gem.c365 return kmem_cache_zalloc(dev_priv->objects, GFP_KERNEL); in i915_gem_object_alloc()
371 kmem_cache_free(dev_priv->objects, obj); in i915_gem_object_free()
4989 dev_priv->objects = in i915_gem_load()
Di915_drv.h1703 struct kmem_cache *objects; member
/linux-4.4.14/Documentation/RCU/
Drculist_nulls.txt2 objects using SLAB_DESTROY_BY_RCU allocations.
9 A typical RCU linked list managing objects which are
19 if (!try_get_ref(obj)) // might fail for free objects
133 if (!try_get_ref(obj)) // might fail for free objects
DRTFP.txt1779 ,title = {Experience distributing objects in an SMMP OS}
/linux-4.4.14/Documentation/trace/
Devents-kmem.txt6 o Slab allocation of small objects of unknown type (kmalloc)
7 o Slab allocation of small objects of known type
15 1. Slab allocation of small objects of unknown type
28 2. Slab allocation of small objects of known type
/linux-4.4.14/lib/
Ddebugobjects.c1026 HLIST_HEAD(objects); in debug_objects_replace_static_objects()
1033 hlist_add_head(&obj->node, &objects); in debug_objects_replace_static_objects()
1047 hlist_move_list(&objects, &obj_pool); in debug_objects_replace_static_objects()
1051 hlist_move_list(&db->list, &objects); in debug_objects_replace_static_objects()
1053 hlist_for_each_entry(obj, &objects, node) { in debug_objects_replace_static_objects()
1068 hlist_for_each_entry_safe(obj, tmp, &objects, node) { in debug_objects_replace_static_objects()
DKconfig.debug400 kernel to track the life time of various objects and validate
401 the operations on those objects.
404 bool "Debug objects selftest"
410 bool "Debug objects in freed memory"
419 bool "Debug timer objects"
423 timer routines to track the life time of timer objects and
427 bool "Debug work objects"
431 work queue routines to track the life time of work objects and
435 bool "Debug RCU callbacks objects"
441 bool "Debug percpu counter objects"
[all …]
/linux-4.4.14/fs/fscache/
DKconfig60 Maintain a global list of active fscache objects that can be
61 retrieved through /proc/fs/fscache/objects for debugging purposes
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt19 Ability to create long paths to objects and remove arbitrarily huge
35 POHMELFS is based on transactions, which are potentially long-standing objects that live
51 removal of objects and data writing are asynchronous and are sent to
Dinfo.txt50 Maximum number of milliseconds to wait for the mcache objects to be processed.
Dnetwork_protocol.txt47 like partial size of the embedded objects or creation flags.
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt167 for different objects and other resources to userspace. Doing that right
179 explictly. Only go with a more global per-device namespace if the objects
181 that the per-device modeset objects like connectors share a namespace with
182 framebuffer objects, which mostly are not shared at all. A separate
188 command submission ioctl. But then if objects are shareable userspace needs
191 of objects, but consider using inode numbers on your shared file descriptors
209 per-device settings, or for child objects with fairly static lifetimes (like
/linux-4.4.14/drivers/staging/fsl-mc/bus/
DKconfig17 to dynamically create networking hardware objects such as
/linux-4.4.14/drivers/gpu/drm/nouveau/
Dnouveau_usif.c277 list_add(&object->head, &cli->objects); in usif_object_new()
388 list_for_each_entry_safe(object, otemp, &cli->objects, head) { in usif_client_fini()
396 INIT_LIST_HEAD(&cli->objects); in usif_client_init()
Dnouveau_drm.h91 struct list_head objects; member
/linux-4.4.14/Documentation/devicetree/bindings/arm/omap/
Ddmm.txt6 interleaving, optimizing transfer of 2D block objects, and provide MMU-like page
/linux-4.4.14/Documentation/namespaces/
Dresource-control.txt1 There are a lot of kinds of objects in the kernel that don't have
Dcompatibility-list.txt35 from different user namespaces should not access the same IPC objects
/linux-4.4.14/Documentation/driver-model/
Dporting.txt19 In a nutshell, the driver model consists of a set of objects that can
20 be embedded in larger, bus-specific objects. Fields in these generic
21 objects can replace fields in the bus-specific objects.
23 The generic objects must be registered with the driver model core. By
440 fields in the bus-specific representations of these objects. Feel free
Ddriver.txt26 As stated above, struct device_driver objects are statically
/linux-4.4.14/fs/sysfs/
DKconfig7 export internal kernel objects, their attributes, and their
/linux-4.4.14/Documentation/sysctl/
Dvm.txt190 reclaimable slab objects like dentries and inodes. Once dropped, their
195 To free reclaimable slab objects (includes dentries and inodes):
197 To free slab objects and pagecache:
200 This is a non-destructive operation and will not free any dirty objects.
201 To increase the number of objects freed by this operation, the user may run
203 number of dirty objects on the system and create more candidates to be
207 (inodes, dentries, pagecache, etc...) These objects are automatically
211 objects, it may cost a significant amount of I/O and CPU to recreate the
212 dropped objects, especially if they were under heavy use. Because of this,
762 the memory which is used for caching of directory and inode objects.
[all …]
/linux-4.4.14/Documentation/security/
Dcredentials.txt38 userspace programs. Linux has a variety of actionable objects, including:
48 As a part of the description of all these objects there is a set of
53 Amongst the credentials of most objects, there will be a subset that
62 Also amongst the credentials of those objects, there will be a subset that
74 Most of the objects in the system are inactive: they don't act on other
75 objects within the system. Processes/tasks are the obvious exception:
133 applied to all subjects and objects, regardless of their source.
153 The UID and GID are carried by most, if not all, Linux objects, even if in
227 Some work by labelling the objects in a system and then applying sets of
DSmack.txt66 objects. The attributes are stored in the extended attribute security
340 On Smack files of all types, IPC, and tasks can be objects.
365 on what subjects can access which objects, based on the labels attached to
422 many interesting cases where limited access by subjects to objects with
480 File system objects including files, directories, named pipes, symbolic links,
498 IPC objects, message queues, semaphore sets, and memory segments exist in flat
502 Process objects reflect tasks on the system and the Smack label used to access
538 CAP_MAC_OVERRIDE allows the process access to objects it would
670 Smack maintains labels on file system objects using extended attributes. The
749 able to access any object, and objects with that label accessible to
/linux-4.4.14/Documentation/x86/x86_64/
Dcpu-hotplug-spec11 objects by setting the Enabled bit in the LAPIC object to zero.
/linux-4.4.14/Documentation/scsi/
Dosd.txt6 called objects. Objects are intended to contain operating system and application
19 user is intended to be the pNFS-over-objects layout driver, which uses objects
Dscsi_fc_transport.txt81 with rports and scsi target objects underneath it. Currently the FC
192 driver data structures are built up, and device objects created.
321 driver data structures are built up, and device objects created.
415 the transport will teardown the vport objects and complete the vport
Dscsi_mid_low_api.txt506 * Both associated refcounting objects have their refcount set to 1.
524 * Notes: Actually increments the counts in two sub-objects
539 * Notes: Actually decrements the counts in two sub-objects. If the
DChangeLog.lpfc675 structure objects.
1574 * Added code for safety pools for following objects: mbuf/bpl,
/linux-4.4.14/fs/jffs2/
DREADME.Locking103 in-core jffs2_inode_cache objects (each inode in JFFS2 has the
155 xattr related objects which include stuff in superblock and ic->xref.
161 of those objects. Thus, a series of processes is often required to retry,
/linux-4.4.14/arch/arm/include/asm/
Dkvm_host.h81 void *objects[KVM_NR_MEM_OBJS]; member
/linux-4.4.14/Documentation/filesystems/nfs/
Dpnfs.txt61 layout types: "files", "objects", "blocks", and "flexfiles". For each
71 objects-layout setup
DExporting40 However when objects are included into the dcache by interpreting a
45 1/ The dcache must sometimes contain objects that are not part of the
Drpc-cache.txt67 include taking references to shared objects.
/linux-4.4.14/Documentation/cpu-freq/
Damd-powernow.txt31 from either the PSB table or from ACPI objects. The ACPI support
Dpcc-cpufreq.txt83 or throttle states (_PSS, _TSS and related ACPI objects) to OSPM. Therefore,
/linux-4.4.14/arch/arm64/include/asm/
Dkvm_host.h79 void *objects[KVM_NR_MEM_OBJS]; member
/linux-4.4.14/drivers/staging/android/
DKconfig52 bool "Software synchronization objects"
/linux-4.4.14/drivers/gpu/drm/sti/
DNOTES39 These IP are mapped to the DRM objects as following:
/linux-4.4.14/Documentation/kbuild/
Dmakefiles.txt202 compile the objects listed in $(isdn-y) and then run
205 Due to kbuild recognizing $(<module_name>-y) for composite objects,
221 Note: Of course, when you are building objects into the kernel,
235 There is also the possibility to list objects that will
237 All objects listed with lib-y are combined in a single
242 For consistency, objects listed in lib-m will be included in lib.a.
261 A Makefile is only responsible for building objects in its own
629 Host programs can be made up based on composite objects.
630 The syntax used to define composite objects for host programs is
631 similar to the syntax used for kernel objects.
[all …]
/linux-4.4.14/Documentation/arm64/
Dmemory.txt94 0000004000000000 0000007fffffffff 256GB kernel objects mapped in HYP
Dacpi_object_usage.txt276 The expectations on individual ACPI objects are discussed in the list that
549 While this may change in the future, there are several classes of objects
577 While these objects have x86 equivalents, and they do make some sense in ARM
Darm-acpi.txt248 on the contents of _DSM objects will be more difficult to maintain over
/linux-4.4.14/Documentation/power/powercap/
Dpowercap.txt11 form of a tree of objects. The objects at the root level of the tree represent
/linux-4.4.14/mm/kasan/
Dreport.c133 page->objects * cache->size; in print_address_description()
/linux-4.4.14/include/linux/
Dmm_types.h103 unsigned objects:15; member
/linux-4.4.14/security/tomoyo/
DKconfig25 Some programs access thousands of objects, so running
/linux-4.4.14/net/sctp/
DKconfig57 type of objects that are currently allocated. This is useful for
/linux-4.4.14/Documentation/cpuidle/
Dsysfs.txt15 following objects are visible instead.
/linux-4.4.14/arch/frv/
DKconfig307 bool "Put data objects of up to 8 bytes into GP-REL"
310 bool "Put data objects of up to 4 bytes into GP-REL"
/linux-4.4.14/Documentation/powerpc/
Ddscr.txt8 support for DSCR, related kernel objects, it's functionalities and exported
/linux-4.4.14/drivers/gpu/drm/msm/
DNOTES33 The kms module provides the plane, crtc, and encoder objects, and
/linux-4.4.14/Documentation/firmware_class/
DREADME115 Note: this would require the persistent objects to be included
/linux-4.4.14/kernel/power/
DKconfig130 objects with the help of a sysfs-based interface.
169 fields of device objects from user space. If you are not a kernel
/linux-4.4.14/arch/arm/kvm/
Dmmu.c137 cache->objects[cache->nobjs++] = page; in mmu_topup_memory_cache()
145 free_page((unsigned long)mc->objects[--mc->nobjs]); in mmu_free_memory_cache()
153 p = mc->objects[--mc->nobjs]; in mmu_memory_cache_alloc()
/linux-4.4.14/drivers/thermal/
DKconfig347 as the master, and INT3401~INT340B ACPI device objects as the slaves.
349 from these objects to userspace via the normal thermal framework.
/linux-4.4.14/init/
DKconfig1049 the amount of memory used by kernel objects in the system. Those are
1173 Provides the way to make tasks work with different objects using
1174 the same id. For example same IPC id may refer to different objects
1193 different IPC objects in different namespaces.
1724 well in all environments. It organizes cache hot objects in
1731 instead of managing queues of cached objects (SLAB approach).
1732 Per cpu caching is realized using slabs of objects instead
1733 of queues of objects. SLUB can use memory efficiently
1752 Per cpu partial caches accellerate objects allocation and freeing
/linux-4.4.14/Documentation/crypto/
Dapi-intro.txt21 'Transforms' are user-instantiated objects, which maintain state, handle all
/linux-4.4.14/arch/x86/kvm/
Dmmu.c666 while (cache->nobjs < ARRAY_SIZE(cache->objects)) { in mmu_topup_memory_cache()
670 cache->objects[cache->nobjs++] = obj; in mmu_topup_memory_cache()
684 kmem_cache_free(cache, mc->objects[--mc->nobjs]); in mmu_free_memory_cache()
694 while (cache->nobjs < ARRAY_SIZE(cache->objects)) { in mmu_topup_memory_cache_page()
698 cache->objects[cache->nobjs++] = page; in mmu_topup_memory_cache_page()
706 free_page((unsigned long)mc->objects[--mc->nobjs]); in mmu_free_memory_cache_page()
740 p = mc->objects[--mc->nobjs]; in mmu_memory_cache_alloc()
/linux-4.4.14/drivers/staging/unisys/Documentation/
Doverview.txt83 The actual struct device objects that correspond to each virtual bus and
84 each virtual device are created and owned by visorbus. These device objects
/linux-4.4.14/Documentation/networking/
Dswitchdev.txt323 XXX: Currently, only SWITCHDEV_OBJ_ID_IPV4_FIB objects are supported.
394 cleanup of the queued-up objects.
/linux-4.4.14/drivers/ata/
DKconfig54 This option adds support for ATA-related ACPI objects.
55 These ACPI objects add the ability to retrieve taskfiles
57 These objects may be related to performance, security,
/linux-4.4.14/Documentation/cgroups/
Dmemcg_test.txt12 2 objects are used.
Dcgroups.txt175 cgroup_subsys_state objects, one for each cgroup subsystem
179 cgroup_subsys_state objects. This is because accessing the
269 that comprise it, a set of cg_cgroup_link objects form a lattice;
Dmemory.txt313 from inside the memcg. The creation is done lazily, so some objects can still be
314 skipped while the cache is being created. All objects in a slab page should
413 test because it has noise of shared objects/status.
/linux-4.4.14/fs/affs/
DChanges288 - The names of newly created filesystem objects are
/linux-4.4.14/Documentation/filesystems/configfs/
Dconfigfs.txt16 kernel objects, configfs is a filesystem-based manager of kernel
17 objects, or config_items.
/linux-4.4.14/Documentation/s390/
Ddriver-model.txt235 Please note, that unlike /proc/chpids in 2.4, the channel path objects reflect
DDebugging390.txt458 all globals & shared library objects are found using this pointer.
/linux-4.4.14/Documentation/hid/
Duhid.txt24 write()'ing "struct uhid_event" objects. Non-blocking operations are supported
Dhid-transport.txt57 They allocate HID device objects and register them with HID core. Transport
/linux-4.4.14/Documentation/development-process/
D4.Coding238 - DEBUG_OBJECTS will add code to track the lifetime of various objects
240 you are adding a subsystem which creates (and exports) complex objects
/linux-4.4.14/Documentation/power/
Ddevices.txt88 device driver level, are implemented by defining and populating objects of type
125 struct dev_pm_ops objects and it is suitable only for implementing system sleep
152 All device objects in the driver model contain fields that control the handling
/linux-4.4.14/arch/x86/include/asm/
Dkvm_host.h188 void *objects[KVM_NR_MEM_OBJS]; member
/linux-4.4.14/Documentation/video4linux/
Dv4l2-controls.txt31 There are two main objects:
37 list of v4l2_ctrl objects that it owns and another list of references to
/linux-4.4.14/Documentation/networking/dsa/
Ddsa.txt340 As of today, the only SWITCHDEV objects supported by DSA are the FDB and VLAN
341 objects.
/linux-4.4.14/Documentation/gpio/
Dconsumer.txt346 the _CRS configuration objects of devices. Those resources do not provide
/linux-4.4.14/Documentation/i2c/
Dwriting-clients142 create i2c_client objects for each I2C device.
/linux-4.4.14/Documentation/input/
Dmulti-touch-protocol.txt11 objects in direct contact with the device surface, is needed. This
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/ce/fuc/
Dcom.fuc268 // load dma objects back into TARGET regs
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic7xxx.seq2153 * an array of 32byte objects, SINDEX contains
2166 * an array of 64byte objects, SINDEX contains
2177 * index into an array of 1byte objects, SINDEX contains
/linux-4.4.14/drivers/block/
DKconfig533 a block device over objects stored in the Ceph distributed object
/linux-4.4.14/drivers/staging/lustre/
Dsysfs-fs-lustre311 Displays number of lock resources (objects on which individual
/linux-4.4.14/Documentation/nvdimm/
Dnvdimm.txt789 For the given example above, here is the view of the objects as seen by the
/linux-4.4.14/scripts/genksyms/
Dparse.tab.c_shipped420 /* Copy COUNT objects from SRC to DST. The source and destination do
/linux-4.4.14/scripts/dtc/
Ddtc-parser.tab.c_shipped417 /* Copy COUNT objects from SRC to DST. The source and destination do