Searched full:matching (Results 1 – 25 of 251) sorted by relevance
1234567891011
| /Documentation/infiniband/ |
| D | tag_matching.rst | 2 Tag matching logic
5 The MPI standard defines a set of rules, known as tag-matching, for matching
17 matching operation. However, this doesn’t imply that tags are consumed in
19 earlier tags can’t be used to satisfy the matching rules.
23 corresponding matching receive is posted. If a matching receive is posted,
25 Implementations frequently use different matching schemes for these two
26 different matching instances.
35 2. The Rendezvous Protocol - the sender sends the tag-matching header,
38 the header to initiate an RDMA READ operation directly to the matching buffer.
41 Tag matching implementation
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-amba | 6 will override standard OF, ACPI, ID table, and name matching.
7 When specified, only a driver with a name matching the value
12 This returns the device to standard matching rules binding.
16 matching name is currently loaded in the kernel, the device will
|
| D | sysfs-bus-vmbus | 6 will override standard static and dynamic ID matching. When
7 specified, only a driver with a name matching the value written
12 This returns the device to standard matching rules binding.
16 matching name is currently loaded in the kernel, the device
|
| D | sysfs-bus-platform | 6 will override standard OF, ACPI, ID table, and name matching.
7 When specified, only a driver with a name matching the value
13 matching rules binding. Writing to driver_override does not
16 driver with a matching name is currently loaded in the kernel,
|
| D | sysfs-bus-css | 39 specified, only a driver with a name matching the value written
44 This returns the device to standard matching rules binding.
48 matching name is currently loaded in the kernel, the device
55 file does not allow to override basic matching rules. I.e.,
|
| D | sysfs-bus-wmi | 6 will override standard ID table matching.
7 When specified, only a driver with a name matching the value
13 driver_override) which returns the device to standard matching
17 load the specified driver. If no driver with a matching name is
|
| D | sysfs-bus-vdpa | 44 When specified, only a driver with a name matching the value
49 This returns the device to standard matching rules binding.
53 matching name is currently loaded in the kernel, the device will
|
| /Documentation/devicetree/bindings/hsi/ |
| D | omap-ssi.txt | 11 - reg: Contains a matching register specifier for each entry
14 - interrupts: Contains matching interrupt information for each entry
22 - clocks: Contains a matching clock specifier for each entry in
34 - reg: Contains a matching register specifier for each entry
|
| /Documentation/admin-guide/ |
| D | binfmt-misc.rst | 9 with which binary. Binfmt_misc recognises the binary-type by matching some bytes
33 Ignored when using filename extension matching.
35 is the byte sequence binfmt_misc is matching for. The magic string
40 If you chose filename extension matching, this is the extension to be
42 Extension matching is case sensitive, and slashes ``/`` are not allowed!
45 bits from matching by supplying a string like magic and as long as magic.
48 filename extension matching.
|
| /Documentation/admin-guide/perf/ |
| D | imx-ddr.rst | 37 --AXI_ID defines AxID matching value.
38 --AXI_MASKING defines which bits of AxID are meaningful for the matching.
41 - 1: corresponding bit is not masked, i.e. used to do the matching.
44 When non-masked bits are matching corresponding AXI_ID bits then counter is
|
| /Documentation/networking/ |
| D | fib_trie.rst | 129 If we don't find a match, we enter prefix matching mode. The prefix length,
131 and we backtrack upwards through the trie trying to find a longest matching
135 Inside each tnode, the search for longest matching prefix consists of searching
141 chop off part of the key in order to find the longest matching prefix.
|
| D | secid.rst | 11 matching labeled xfrm(s).
|
| D | tcp_ao.rst | 119 connection. Find the matching MKT for this segment, using the segment's
123 i. If there is no matching MKT, remove TCP-AO from the segment.
136 the AO option not matching an MKT.
140 Connections not matching any MKT do not require TCP-AO. Further, incoming
153 >> All TCP segments MUST be checked against the set of MKTs for matching
169 user explicitly, or by a matching rule?
184 2. If the matching MKT corresponding to the segment’s socket pair and
189 Q: If both peers have multiple MKTs matching the connection's socket pair
285 | Matching of MKTs | half-problem: only | hard |
349 RFC 5925 very permissively specifies how TCP port matching can be done for
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | method-tracing.rst | 200 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
206 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
212 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
218 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
224 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
|
| /Documentation/driver-api/usb/ |
| D | hotplug.rst | 97 be used when matching a driver to a device or class of devices. The
103 ... matching devices with specified vendor and product ids
107 ... matching specified interface class info
109 ... matching specified device class info
|
| /Documentation/driver-api/pldmfw/ |
| D | driver-ops.rst | 26 package data in a record to the device firmware. If the matching record
36 that is, for each component indicated by the matching record. The
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 80 corresponding frame to the matching capture buffer.
129 of macroblocks to decode a full corresponding frame to the matching
170 of macroblocks to decode a full corresponding frame to the matching
193 of macroblocks to decode a full corresponding frame to the matching
274 of macroblocks to decode a full corresponding frame to the matching
|
| /Documentation/networking/device_drivers/fddi/ |
| D | defza.rst | 34 The board supports a 64-entry CAM for matching destination addresses.
53 matching against the original address though.
|
| /Documentation/usb/ |
| D | gadget_uvc.rst | 131 Color Matching Descriptors
135 skipped; those default values follow those defined in the Color Matching Descriptor
138 To create a Color Matching Descriptor, create a configfs item and set its three
144 # Create a new Color Matching Descriptor
155 # Create a symlink to the Color Matching Descriptor from the format's config item
159 default color matching descriptor exists and is used by any format which does
160 not have a link to a different Color Matching Descriptor. It's possible to
|
| /Documentation/driver-api/ |
| D | pwrseq.rst | 72 Dynamic consumer matching
76 mechanism for dynamic matching of consumers and providers. Every power sequence
|
| /Documentation/devicetree/bindings/arm/ |
| D | primecell.yaml | 15 driver matching.
|
| /Documentation/devicetree/bindings/sound/ |
| D | brcm,bcm63xx-audio.txt | 11 - clock-names: One of each entry matching the clocks phandles list:
|
| /Documentation/pcmcia/ |
| D | devicetable.rst | 5 Matching of PCMCIA devices to drivers is done using one or more of the
|
| /Documentation/devicetree/bindings/mmc/ |
| D | arm,pl18x.yaml | 158 The GPIO matching the CMD pin.
163 The GPIO matching the CK pin.
168 The GPIO matching the CKIN pin.
|
| /Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu.yaml | 178 SMMUs with stream matching support and complex masters may use a value of
213 For SMMUs supporting stream matching and using #iommu-cells = <1>,
214 specifies a mask of bits to ignore when matching stream IDs (e.g. this may
219 using stream matching with #iommu-cells = <2>, and may be ignored if
595 /* SMMU with stream matching or stream indexing */
616 /* SMMU with stream matching */
|
1234567891011