| /linux-4.1.27/tools/perf/Documentation/ |
| D | examples.txt | 66 well. For example the page allocations done by a 'git gc' can be
77 To check which functions generated page allocations:
120 allocations - to see precisely what kind of page allocations there
157 Or you can observe the whole system's page allocations for 10
173 Or observe how fluctuating the page allocations are, via statistical
190 and check which instructions/source-code generated page allocations:
209 ( this shows that 83.42% of __GI___fork's page allocations come from
|
| /linux-4.1.27/Documentation/ |
| D | flexible-arrays.txt | 5 Large contiguous memory allocations can be unreliable in the Linux kernel.
10 vmalloc() allocations can require expensive cross-processor interrupts on
21 reasonably well. Only single-page allocations are made, so memory
57 the array was created). If any memory allocations must be performed, flags
65 trick is to ensure that any needed memory allocations are done before
|
| D | kmemleak.txt | 72 The memory allocations via kmalloc, vmalloc, kmem_cache_alloc and
203 Page allocations and ioremap are not tracked.
|
| D | IRQ-domain.txt | 7 that each one gets assigned non-overlapping allocations of Linux
129 controller to manage IRQ allocations and it requires an irq_desc to be
|
| D | remoteproc.txt | 297 allocation of virtio devices. Dynamic allocations will also be made possible
298 using the rpmsg bus (similar to how we already do dynamic allocations of
|
| D | DMA-API-HOWTO.txt | 159 one platform (SGI SN2) requires 64-bit consistent allocations to
182 The query for consistent allocations is performed via a call
241 If a card is capable of using 64-bit consistent allocations as well,
259 uses consistent allocations, one would have to check the return value from
|
| D | BUG-HUNTING | 236 Debug memory allocations. This will help you see whether data has been
|
| D | kernel-parameters.txt | 422 to be done where GFP_KERNEL allocations are allowed.
662 contiguous memory allocations and optionally the
664 memory allocations. A value of 0 disables CMA
677 allocations, by default set to 256K.
1632 for non-movable allocations. The requested amount is
1642 Note that allocations like PTEs-from-HighMem still
2106 amount of memory used for migratable allocations.
2111 that the amount of memory usable for all allocations
2796 if allocations done by BIOS are too small to
3845 [X86] Flags controlling user PTE allocations.
|
| D | vme_api.txt | 110 Functions are also provided to free window allocations once they are no longer
|
| D | nommu-mmap.txt | 286 aggressively trim allocations and discard any excess pages back in to the page
|
| D | rpmsg.txt | 276 At this point we only support dynamic allocations of rpmsg channels.
|
| D | kmemcheck.txt | 86 / "Debug page memory allocations".
640 will keep kmemcheck from checking and reporting certain allocations. Here
|
| D | DMA-API.txt | 549 region only at the granularity of a page. For smaller allocations,
|
| D | devices.txt | 28 allocations have already been removed.
|
| /linux-4.1.27/drivers/staging/netlogic/ |
| D | TODO | 2 * All memory allocation should be changed to DMA allocations
|
| /linux-4.1.27/Documentation/vm/ |
| D | balance | 4 __GFP_IO allocations.
6 There are two reasons to be requesting non __GFP_WAIT allocations:
59 for non-sleepable allocations. Second, the HIGHMEM zone is also balanced,
61 HIGHMEM page, as well as to ensure that HIGHMEM allocations do not
|
| D | numa | 78 memory, Linux must decide whether to order the zonelists such that allocations
123 So, default, local allocations will succeed with the kernel supplying the
125 allows such allocations to fallback to other nearby nodes when a node that
128 Some kernel allocations do not want or cannot tolerate this allocation fallback
149 allocations will be attempted.
|
| D | numa_memory_policy.txt | 27 is the policy that governs all page allocations that aren't controlled
31 default policy will be set to interleave allocations across all nodes
33 with boot-time allocations.
36 for a specific task, this policy controls all page allocations made by or
38 If a task does not define a task policy, then all page allocations that
121 As mentioned above [re: VMA policies], allocations of page cache
191 MPOL_INTERLEAVED: This mode specifies that page allocations be
|
| D | overcommit-accounting | 24 memory allocations will be available in the future
|
| D | transhuge.txt | 57 feature that applies to all dynamic high order allocations in the
77 lived page allocations even for hugepage unaware applications that
219 successfully allocated. It includes allocations which where
254 using the mm_page_alloc tracepoint to identify which allocations were
|
| D | slub.txt | 115 governed by the order of the allocation for each slab. The allocations
124 In general slub will be able to perform this number of allocations
|
| /linux-4.1.27/arch/arc/ |
| D | Kconfig.debug | 12 on the VM subsystem for higher order allocations.
|
| /linux-4.1.27/arch/m32r/ |
| D | Kconfig.debug | 6 bool "Debug page memory allocations"
|
| /linux-4.1.27/drivers/misc/ |
| D | vmw_balloon.c | 513 unsigned int allocations = 0; in vmballoon_inflate() local
587 if (++allocations > VMW_BALLOON_YIELD_THRESHOLD) { in vmballoon_inflate()
589 allocations = 0; in vmballoon_inflate()
|
| /linux-4.1.27/mm/ |
| D | Kconfig.debug | 11 bool "Debug page memory allocations"
|
| D | Kconfig | 95 # allocations when memory_present() is called. If this cannot
603 access allocations that span two pages. However, if a particular
|
| /linux-4.1.27/arch/metag/ |
| D | Kconfig.debug | 16 on the VM subsystem for higher order allocations. This option
|
| /linux-4.1.27/security/selinux/include/ |
| D | avc.h | 44 unsigned int allocations; member
|
| /linux-4.1.27/Documentation/fault-injection/ |
| D | fault-injection.txt | 102 highmem/user allocations.
109 only into non-sleep allocations (GFP_ATOMIC allocations).
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | vm.txt | 230 tending towards 0 imply allocations would fail due to lack of memory,
294 So the Linux page allocator has a mechanism which prevents allocations
300 mechanism will also defend that region from allocations which could use
433 allocations; if you set this to lower than 1024KB, your system will
510 NOMMU mmap allocations.
512 A value of 0 disables trimming of allocations entirely, while a value of 1
514 trimming of allocations is initiated.
811 Allowing regular swap effectively restricts allocations to the local
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | fake-numa-for-cpusets | 47 memory allocations (1G).
|
| /linux-4.1.27/arch/sh/ |
| D | Kconfig.debug | 38 on the VM subsystem for higher order allocations. This option
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.ips | 40 4.71.00 - Change all memory allocations to not use GFP_DMA flag
|
| D | ChangeLog.sym53c8xx_2 | 136 All driver memory allocations are now not greater than 1 PAGE
|
| D | ChangeLog.lpfc | 64 - don't call dma_sync function on allocations from
131 * Removed last of GFP_ATOMIC allocations.
245 * Reduced used of GFP_ATOMIC for memory allocations.
|
| D | sym53c8xx_2.txt | 343 alloc: print info about memory allocations (ccb, lcb)
|
| D | ncr53c8xx.txt | 493 alloc: print info about memory allocations (ccb, lcb)
|
| /linux-4.1.27/Documentation/frv/ |
| D | configuring.txt | 52 reserved will not be available for normal allocations.
|
| /linux-4.1.27/Documentation/devicetree/bindings/reserved-memory/ |
| D | reserved-memory.txt | 98 /* global autoconfigured region for contiguous allocations */
|
| /linux-4.1.27/Documentation/RCU/ |
| D | rculist_nulls.txt | 2 objects using SLAB_DESTROY_BY_RCU allocations.
|
| D | torture.txt | 245 o "rtaf": Number of allocations from the torture freelist that have
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-power | 179 the amount of memory reserved for allocations made by device
182 will be used as the amount of memory to reserve for allocations
|
| D | sysfs-kernel-slab | 38 locations from which allocations for this cache were performed.
480 The trace file specifies whether object allocations and frees
|
| /linux-4.1.27/Documentation/trace/ |
| D | events-kmem.txt | 104 high-order allocations will start failing at some time in the future. One
|
| D | tracepoint-analysis.txt | 259 noticed that X was generating an insane amount of page allocations so let's look
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | xfs.txt | 161 Data allocations will not be aligned at stripe unit
214 Data allocations will be rounded up to stripe width boundaries
|
| D | btrfs.txt | 44 Debugging option to force all block allocations above a certain
|
| D | sharedsubtree.txt | 923 if any memory allocations fail, go to the abort phase.
|
| D | proc.txt | 916 (mode 2 in 'vm.overcommit_memory'),allocations which would
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | cpusets.txt | 233 i.e. it restricts kernel allocations for page, buffer and other data
235 whether hardwalled or not, restrict allocations of memory for user
332 Setting memory spreading causes allocations for the affected page
338 applies to memory page allocations.
661 kernel internal allocations that must be satisfied, immediately.
|
| D | unified-hierarchy.txt | 369 conservatively. When hit, it throttles allocations by forcing them
377 In extreme cases, with many concurrent allocations and a complete
|
| D | cgroups.txt | 555 Called after @cgrp successfully completed all allocations and made
629 post-attachment activity that requires memory allocations or blocking.
|
| D | memory.txt | 782 allocations. Monitoring this reclaiming activity might be useful for
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | devres.txt | 207 resource allocations already do the job.
|
| /linux-4.1.27/security/selinux/ |
| D | avc.c | 279 avc_cache_stats_incr(allocations); in avc_alloc_node()
|
| D | selinuxfs.c | 1411 hits, misses, st->allocations, in sel_avc_stats_seq_show()
|
| /linux-4.1.27/fs/jffs2/ |
| D | README.Locking | 15 obtained during space allocations (jffs2_reserve_space()) and freed
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | videobuf | 291 means that these drivers may be trying to do high-order allocations at any
298 allocations will not meet that criterion, but buffers obtained from other
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 4.Coding | 276 especially where memory allocations are involved. With fault injection
277 enabled, a configurable percentage of memory allocations will be made to
|
| /linux-4.1.27/arch/m68k/ |
| D | Kconfig.machine | 322 on the VM subsystem for higher order allocations.
|
| /linux-4.1.27/Documentation/networking/ |
| D | packet_mmap.txt | 367 All memory allocations are not freed until the socket is closed. The memory
368 allocations are done with GFP_KERNEL priority, this basically means that
|
| /linux-4.1.27/fs/befs/ |
| D | ChangeLog | 159 * Made inode allocations use a slab cache
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 481 memory allocations made are satisfied.
560 and the gfp argument is used to control how any memory allocations made are
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 447 bool "Debug slab memory allocations"
501 allocations. See Documentation/kmemleak.txt for more
516 Kmemleak must track all the memory allocations to avoid
|
| /linux-4.1.27/Documentation/usb/ |
| D | WUSB-Design-overview.txt | 294 among them are the bandwidth allocations that tell each device
|
| /linux-4.1.27/arch/alpha/ |
| D | Kconfig | 633 allocations. This equates to about 8GB.
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | mmu.txt | 26 - reliability: avoid multipage or GFP_ATOMIC allocations
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci.txt | 266 [ OS BUG: we don't check resource allocations before enabling those
|
| /linux-4.1.27/arch/powerpc/ |
| D | Kconfig | 1026 is used to make consistent memory allocations.
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | booting-without-of.txt | 413 and thus not to be used for memory allocations, especially during
416 MMU hash table, etc... Those allocations must be done in such a
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | CHANGES | 393 Reduce the number of large buffer allocations in cifs response processing
|
| /linux-4.1.27/Documentation/security/ |
| D | keys.txt | 1220 after all allocations and other potentially failing function calls are
|
| /linux-4.1.27/Documentation/block/ |
| D | biodoc.txt | 592 deadlock-free allocations during extreme VM load. For example, the VM
|
| /linux-4.1.27/arch/arm/ |
| D | Kconfig | 116 virtual space with just a few allocations.
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | ALSA-Configuration.txt | 608 fake_buffer - Fake buffer allocations (default = 1)
|