Searched refs:orders (Results 1 – 13 of 13) sorted by relevance
/linux-4.1.27/drivers/staging/android/ion/ |
D | ion_system_heap.c | 32 static const unsigned int orders[] = {8, 4, 0}; variable 33 static const int num_orders = ARRAY_SIZE(orders); 39 if (order == orders[i]) in order_to_index() 105 if (size < order_to_size(orders[i])) in alloc_largest_available() 107 if (max_order < orders[i]) in alloc_largest_available() 110 page = alloc_buffer_page(heap, buffer, orders[i]); in alloc_largest_available() 134 unsigned int max_order = orders[0]; in ion_system_heap_allocate() 279 if (orders[i] > 4) in ion_system_heap_create() 281 pool = ion_page_pool_create(gfp_flags, orders[i]); in ion_system_heap_create()
|
/linux-4.1.27/drivers/usb/ |
D | Kconfig | 132 Note however that some operations are three orders of magnitude
|
/linux-4.1.27/tools/virtio/virtio-trace/ |
D | README | 9 - controlled by start/stop orders from a Host
|
/linux-4.1.27/Documentation/vm/ |
D | pagemap.txt | 80 The buddy system organizes free memory in blocks of various orders.
|
D | slub.txt | 46 caused higher minimum slab orders
|
/linux-4.1.27/Documentation/sysctl/ |
D | vm.txt | 549 "Node order" orders the zonelists by node, then by zone within each node. 552 "Zone Order" orders the zonelists by zone type, then by node within each
|
/linux-4.1.27/Documentation/ |
D | ManagementStyle | 16 companies. If you sign purchase orders or you have any clue about the
|
D | memory-barriers.txt | 1299 The key point is that although CPU 2's read barrier orders its pair 1787 combined with a following ACQUIRE, orders prior loads against 1788 subsequent loads and stores and also orders prior stores against 1897 The operations will always occur in one of the following orders: 1905 the more strongly ordered systems may rule out some of the above orders.
|
D | atomic_ops.txt | 625 strictly orders all subsequent memory operations (including
|
D | SubmittingPatches | 157 to do frotz", as if you are giving orders to the codebase to change
|
/linux-4.1.27/Documentation/filesystems/ |
D | porting | 469 need now. Remember that they have opposite orders of arguments ;-/
|
/linux-4.1.27/Documentation/virtual/kvm/ |
D | api.txt | 3524 This capability controls which SIGP orders will be handled completely in user 3525 space. With this capability enabled, all fast orders will be handled completely 3533 All other orders will be handled completely in user space. 3537 old way of handling SIGP orders is used (partially in kernel and user space).
|
/linux-4.1.27/Documentation/m68k/ |
D | kernel-options.txt | 630 one LUN, and the SCSI device itself orders the requests so they
|