Searched full:order (Results 1 – 25 of 1201) sorted by relevance
12345678910>>...49
| /Documentation/netlink/specs/ |
| D | nftables.yaml | 23 byte-order: big-endian
242 byte-order: big-endian
253 byte-order: big-endian
260 byte-order: big-endian
265 byte-order: big-endian
281 byte-order: big-endian
295 byte-order: big-endian
300 byte-order: big-endian
314 byte-order: big-endian
321 byte-order: big-endian
[all …]
|
| D | ovs_flow.yaml | 57 byte-order: big-endian
65 byte-order: big-endian
70 byte-order: big-endian
93 byte-order: big-endian
99 byte-order: big-endian
104 byte-order: big-endian
149 byte-order: big-endian
153 byte-order: big-endian
161 byte-order: big-endian
165 byte-order: big-endian
[all …]
|
| D | nfsd.yaml | 16 byte-order: big-endian
38 byte-order: big-endian
43 byte-order: big-endian
56 byte-order: big-endian
60 byte-order: big-endian
|
| D | tc.yaml | 1101 byte-order: big-endian
1105 byte-order: big-endian
1141 byte-order: big-endian
1154 byte-order: big-endian
1594 byte-order: big-endian
1598 byte-order: big-endian
1608 byte-order: big-endian
1612 byte-order: big-endian
1751 byte-order: big-endian
1923 byte-order: big-endian
[all …]
|
| D | tcp_metrics.yaml | 29 byte-order: big-endian
36 byte-order: big-endian
70 byte-order: big-endian
77 byte-order: big-endian
|
| /Documentation/userspace-api/media/v4l/ |
| D | field-order.rst | 3 .. _field-order:
6 Field Order
25 which field of a frame is older, the *temporal order*.
30 even) fields, the *spatial order*: The first line of the top field is
39 creating a natural order.
44 and spatial order of fields. The diagrams below should make this
48 bus in the same order they were captured, so if the top field was
53 order. Some drivers may permit the selection of a different order, to
76 - Applications request this field order when any field format
78 e.g. the requested image size, and return the actual field order.
[all …]
|
| /Documentation/trace/postprocess/ |
| D | trace-vmscan-postprocess.pl | 31 # Per-order events
110 my $regex_direct_begin_default = 'order=([0-9]*) gfp_flags=([A-Z_|]*)';
112 my $regex_kswapd_wake_default = 'nid=([0-9]*) order=([0-9]*)';
114 my $regex_wakeup_kswapd_default = 'nid=([0-9]*) order=([0-9]*) gfp_flags=([A-Z_|]*)';
115 my $regex_lru_isolate_default = 'classzone=([0-9]*) order=([0-9]*) nr_requested=([0-9]*) nr_scanned…
166 # Verify fields are in the right order
187 "order", "gfp_flags");
195 "nid", "order");
203 "nid", "order", "gfp_flags");
207 "classzone", "order",
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | fsl-vdoa.txt | 1 Freescale Video Data Order Adapter
4 The Video Data Order Adapter (VDOA) is present on the i.MX6q. Its sole purpose
5 is to reorder video data from the macroblock tiled order produced by the CODA
6 960 VPU to the conventional raster-scan order for scanout.
|
| D | st,st-hva.txt | 8 order.
13 - clock-names: names of the clocks listed in clocks property in the same order.
|
| /Documentation/admin-guide/mm/ |
| D | swap_numa.rst | 13 Swap device has priority and that decides the order of it to be used. To make
22 Then node 0 will use the two swap devices in the order of swapA then swapB and
23 node 1 will use the two swap devices in the order of swapB then swapA. Note
24 that the order of them being swapped on doesn't matter.
38 Then node 0 will use them in the order of::
44 node 1 will use them in the order of::
48 node 2 will use them in the order of::
55 node 3 will use them in the order of::
|
| /Documentation/sound/soc/ |
| D | pops-clicks.rst | 22 components in a specific order. This order is different for startup and
26 Startup Order :- DAC --> Mixers --> Output PGA --> Digital Unmute
28 Shutdown Order :- Digital Mute --> Output PGA --> Mixers --> DAC
43 Startup Order - Input PGA --> Mixers --> ADC
45 Shutdown Order - ADC --> Mixers --> Input PGA
|
| /Documentation/devicetree/bindings/display/ |
| D | st,stih4xx.txt | 19 order.
37 order.
41 order.
50 the same order.
54 order.
62 the same order.
65 the same order
69 order.
78 the same order.
83 order.
[all …]
|
| D | lvds.yaml | 18 It supports reversing the bit order on the formats defined there in order
26 If set, reverse the bit order described in the data mappings on all
|
| /Documentation/trace/ |
| D | events-kmem.rst | 49 mm_page_alloc page=%p pfn=%lu order=%d migratetype=%d gfp_flags=%s
50 mm_page_alloc_zone_locked page=%p pfn=%lu order=%u migratetype=%d cpu=%d percpu_refill=%d
51 mm_page_free page=%p pfn=%lu order=%d
52 mm_page_free_batched page=%p pfn=%lu order=%d cold=%d
78 mm_page_alloc_zone_locked page=%p pfn=%lu order=%u migratetype=%d cpu=%d percpu_refill=%d
79 mm_page_pcpu_drain page=%p pfn=%lu order=%d cpu=%d migratetype=%d
82 for order-0 pages, reduces contention on the zone->lock and reduces the
109 External fragmentation affects whether a high-order allocation will be
116 high-order allocations will start failing at some time in the future. One
|
| /Documentation/mm/ |
| D | page_frags.rst | 6 which resides within a 0 or higher order compound page. Multiple
16 In order to make use of the page fragment APIs a backing page fragment
36 level. In order to enable these cases it is necessary to provide a generic
40 cleaning up the multiple references that were added to a page in order to
|
| D | slub.rst | 8 SLUB can enable debugging only for selected slabs in order to avoid
12 In order to switch debugging on one can add an option ``slab_debug``
61 F.e. in order to boot just with sanity checks and red zoning one would specify::
70 end of the slab name, in order to cover all slabs with the same prefix. For
81 Debugging options may require the minimum possible slab order to increase as
126 in order to reduce overhead and increase cache hotness of objects.
133 order to do so you must have the ``slabinfo`` tool. Then you can do
150 governed by the order of the allocation for each slab. The allocations
159 slab in order for the allocation order to be acceptable. In
165 specifies a minimum order of slabs. A similar effect like
[all …]
|
| /Documentation/arch/riscv/ |
| D | uabi.rst | 9 The canonical order of ISA extension names in the ISA string is defined in
14 #. Single-letter extensions come first, in canonical order.
15 The canonical order is "IMAFDQLCBKJTPVH".
26 ordered first by category, in canonical order, as listed above, then
41 An example string following the order is::
|
| /Documentation/devicetree/bindings/sound/ |
| D | audio-graph-port.yaml | 28 link-trigger-order:
29 description: trigger order for both start/stop
31 link-trigger-order-start:
32 description: trigger order for start
34 link-trigger-order-stop:
35 description: trigger order for stop
|
| D | st,sti-asoc-card.txt | 20 - clock-names: name of the clocks listed in clocks property in the same order
23 order than the CPU_DAI properties.
26 the same order.
28 - interrupts: CPU_DAI interrupt line, listed in the same order than the
32 order than the CPU_DAI properties.
39 - clocks: CPU_DAI IP clock source, listed in the same order than the
|
| /Documentation/devicetree/bindings/ |
| D | dts-coding-style.rst | 47 Order of Nodes
51 ordered by unit address in ascending order.
61 ordered either alpha-numerically or by keeping the order from DTSI, where
92 /* Board DTS - alphabetical order */
102 /* Board DTS - alternative order, keep as DTSI */
112 Order of Properties in Device Node
115 The following order of properties in device nodes is preferred:
|
| /Documentation/security/keys/ |
| D | ecryptfs.rst | 12 the FEK is encrypted by 'ecryptfsd' with the help of external libraries in order
23 format 'ecryptfs' in order to be used in conjunction with the eCryptfs
28 In order to avoid known-plaintext attacks, the datablob obtained through
35 time after the unsealing of a 'trusted' key in order to perform the mount in a
|
| /Documentation/devicetree/bindings/powerpc/4xx/ |
| D | cpm.txt | 10 one of two different order for the CPM
12 in the following order (ER,FR,SR). The
13 others have them in the following order
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-trigger-sysfs | 18 trigger. In order to associate the trigger with an IIO device
28 In order to achieve this, one should write a positive integer
38 created trigger from the list of available triggers. In order to
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 11 always acquire the locks in order by increasing address. We'll call
12 that "inode pointer" order in the following.
47 * take the locks that need to be taken (exclusive), in inode pointer order
57 * lock the parents in "ancestors first" order (exclusive). If neither is an
63 * lock the non-directories involved (exclusive), in inode pointer order.
138 them in order of non-decreasing rank. Namely,
141 order.
153 3. ->i_rwsem of non-directories on that filesystem, in order of
157 6. ->i_rwsem of non-directories on local filesystem, in order of
167 Since the locking order is consistent with the ranking, all
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | lookup-order.rst | 2 Firmware lookup order
6 Below is chronological order of how firmware will be looked for once
|
12345678910>>...49