| /Linux-v5.4/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 …]
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| 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-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-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 | 42 specified, only a driver with a name matching the value written
47 This returns the device to standard matching rules binding.
51 matching name is currently loaded in the kernel, the device
57 file does not allow to override basic matching rules. I.e.,
|
| D | sysfs-wusb_cbaf | 30 - If it has a matching CHID,CDID entry, the device
35 matching CDID in its database), the device is
|
| /Linux-v5.4/net/netfilter/ |
| D | nfnetlink_cttimeout.c | 83 struct ctnl_timeout *timeout, *matching = NULL; in cttimeout_new_timeout() local
104 matching = timeout; in cttimeout_new_timeout()
108 if (matching) { in cttimeout_new_timeout()
113 if (matching->timeout.l3num != l3num || in cttimeout_new_timeout()
114 matching->timeout.l4proto->l4proto != l4num) in cttimeout_new_timeout()
117 return ctnl_timeout_parse_policy(&matching->timeout.data, in cttimeout_new_timeout()
118 matching->timeout.l4proto, in cttimeout_new_timeout()
516 struct ctnl_timeout *timeout, *matching = NULL; in ctnl_timeout_find_get() local
529 matching = timeout; in ctnl_timeout_find_get()
533 return matching ? &matching->timeout : NULL; in ctnl_timeout_find_get()
|
| D | nfnetlink_acct.c | 52 struct nf_acct *nfacct, *matching = NULL; in nfnl_acct_new() local
71 matching = nfacct; in nfnl_acct_new()
75 if (matching) { in nfnl_acct_new()
78 atomic64_set(&matching->pkts, 0); in nfnl_acct_new()
79 atomic64_set(&matching->bytes, 0); in nfnl_acct_new()
82 if ((matching->flags & NFACCT_F_QUOTA)) in nfnl_acct_new()
84 &matching->flags); in nfnl_acct_new()
|
| /Linux-v5.4/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
|
| /Linux-v5.4/Documentation/admin-guide/perf/ |
| D | imx-ddr.rst | 32 --AXI_ID defines AxID matching value.
33 --AXI_MASKING defines which bits of AxID are meaningful for the matching.
35 1: corresponding bit is not masked, i.e. used to do the matching.
38 When non-masked bits are matching corresponding AXI_ID bits then counter is
|
| /Linux-v5.4/Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu.txt | 53 SMMUs with stream matching support and complex masters
73 - stream-match-mask : For SMMUs supporting stream matching and using
75 when matching stream IDs (e.g. this may be programmed
81 or using stream matching with #iommu-cells = <2>, and
112 /* SMMU with stream matching or stream indexing */
133 /* SMMU with stream matching */
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/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"
|
| /Linux-v5.4/drivers/staging/iio/Documentation/ |
| D | inkernel.txt | 44 * matching dev or dev_name against consumer_dev and consumer_dev_name
45 * matching consumer_channel against consumer_channel in the map
|
| /Linux-v5.4/tools/testing/selftests/rcutorture/bin/ |
| D | functions.sh | 25 echo $1 needs argument $2 matching \"$5\"
|
| /Linux-v5.4/Documentation/networking/ |
| D | fib_trie.txt | 125 If we don't find a match, we enter prefix matching mode. The prefix length,
127 and we backtrack upwards through the trie trying to find a longest matching
131 Inside each tnode, the search for longest matching prefix consists of searching
137 chop off part of the key in order to find the longest matching prefix.
|
| D | defza.txt | 28 The board supports a 64-entry CAM for matching destination addresses.
47 matching against the original address though.
|
| /Linux-v5.4/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
|
| /Linux-v5.4/tools/memory-model/ |
| D | linux-kernel.bell | 43 (* Compute matching pairs of nested Rcu-lock and Rcu-unlock *)
59 (* Compute matching pairs of nested Srcu-lock and Srcu-unlock *)
|
| /Linux-v5.4/Documentation/devicetree/bindings/media/ |
| D | exynos-jpeg-codec.txt | 15 matching entries in the clock-names property; from
|
| /Linux-v5.4/Documentation/devicetree/bindings/iio/dac/ |
| D | vf610-dac.txt | 11 - clock-names: Must contain "dac" matching entry in the clocks property.
|
| /Linux-v5.4/drivers/staging/fwserial/ |
| D | TODO | 9 GUID-to-port matching/whitelist/blacklist.
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-probe.txt | 176 …d '%return' means that it probes function return. And ';PTN' means lazy matching pattern (see LAZY…
177 …lazy matching by using 'SRC:ALN' or 'SRC;PTN' syntax, where 'SRC' is the source file path, ':ALN' …
229 …The lazy line matching is similar to glob matching but ignoring spaces in both of pattern and targ…
234 …hedule() can be moved easily by modifying schedule(), but the same line matching 'rq=cpu_rq*' may …
238 The filter pattern is a glob matching pattern(s) to filter variables.
|
| /Linux-v5.4/tools/memory-model/scripts/ |
| D | parseargs.sh | 55 echo $1 needs argument $2 matching \"$5\"
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/dsa/ |
| D | b53.txt | 63 - reg-names: a total of 3 names matching the 3 base register address, must
69 - interrupt-names: a total of 13 names matching the 13 interrupts specified
|
