| /linux/Documentation/infiniband/ |
| H A 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/Documentation/ABI/testing/ |
| H A 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
|
| H A 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
|
| H A 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,
|
| H A 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.,
|
| H A 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
|
| H A 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
|
| /linux/net/netfilter/ |
| H A D | nfnetlink_cttimeout.c | 102 struct ctnl_timeout *timeout, *matching = NULL; in cttimeout_new_timeout() local 123 matching = timeout; in cttimeout_new_timeout() 127 if (matching) { in cttimeout_new_timeout() 132 if (matching->timeout->l3num != l3num || in cttimeout_new_timeout() 133 matching->timeout->l4proto->l4proto != l4num) in cttimeout_new_timeout() 136 return ctnl_timeout_parse_policy(&matching->timeout->data, in cttimeout_new_timeout() 137 matching->timeout->l4proto, in cttimeout_new_timeout() 506 struct ctnl_timeout *timeout, *matching = NULL; in ctnl_timeout_find_get() local 514 matching = timeout; in ctnl_timeout_find_get() 519 return matching in ctnl_timeout_find_get() [all...] |
| H A D | Kconfig | 502 This option adds support for matching on DCCP extension headers. 524 packets matching some criteria. 619 tristate "Netfilter nf_tables xfrm/IPSec security association matching" 630 This option allows matching for the presence or absence of a 638 This option allows matching packets from an specific OS. 765 Netfilter mark matching allows you to match packets based on the 923 This option adds the `IDLETIMER' target. Each matching packet 1163 BPF matching applies a linux socket filter to each packet and 1174 Socket/process control group matching allows you to match locally 1254 It allows matching o [all...] |
| /linux/Documentation/devicetree/bindings/hsi/ |
| H A 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/Documentation/driver-api/driver-model/ |
| H A D | binding.rst | 30 Instead of trying to derive a complex state machine and matching 107 Userspace may override the standard matching by writing a driver name to 110 bypasses all bus-specific matching (OF, ACPI, ID tables, etc.). 113 the device to standard matching rules. Writing to ``driver_override`` 129 its own matching, using ``device_match_driver_override()``:: 139 /* Fall through to bus-specific matching... */
|
| /linux/Documentation/admin-guide/perf/ |
| H A 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
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A 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/Documentation/driver-api/pldmfw/ |
| H A 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
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A D | motorola-cpcap.txt | 35 detect interrupt matching "hs" and microphone bias 2 36 detect interrupt matching "mb2" in interrupt-names.
|
| /linux/drivers/staging/iio/Documentation/ |
| H A 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/Documentation/networking/ |
| H A 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.
|
| /linux/tools/testing/selftests/damon/ |
| H A D | sysfs.py | 98 assert_true(filter_.matching == dump['matching'], 'matching', dump) 256 type_='memcg', matching=True, allow=True, memcg_path='/') 332 _damon_sysfs.DamosFilter(type_='addr', matching=True, 337 _damon_sysfs.DamosFilter(type_='anon', matching=True,
|
| H A D | sysfs_no_op_commit_break.py | 37 matching=True,
|
| /linux/Documentation/networking/device_drivers/fddi/ |
| H A D | defza.rst | 34 The board supports a 64-entry CAM for matching destination addresses. 53 matching against the original address though.
|
| /linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | functions.sh | 25 echo $1 needs argument $2 matching \"$5\"
|
| /linux/lib/kunit/ |
| H A D | Kconfig | 101 string only matching tests are executed. 109 string only matching tests are executed. 117 string only matching tests are executed.
|
| /linux/tools/memory-model/ |
| H A D | linux-kernel.bell | 56 (* Compute matching pairs of nested Rcu-lock and Rcu-unlock *) 72 (* Compute matching pairs of nested Srcu-lock and Srcu-unlock *)
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-probe.txt | 182 'FUNC' specifies a probed function name, and it may have one of the following options; '+OFFS' is the offset from function entry address in bytes, ':RLN' is the relative-line number from function entry line, and '%return' means that it probes function return. And ';PTN' means lazy matching pattern (see LAZY MATCHING). Note that ';PTN' must be the end of the probe point definition. In addition, '@SRC' specifies a source file which has that function. 183 It is also possible to specify a probe point by the source line number or lazy matching by using 'SRC:ALN' or 'SRC;PTN' syntax, where 'SRC' is the source file path, ':ALN' is the line number and ';PTN' is the lazy matching pattern. 235 The lazy line matching is similar to glob matching but ignoring spaces in both of pattern and target. So this accepts wildcards('*', '?') and character classes(e.g. [a-z], [!A-Z]). 240 This provides some sort of flexibility and robustness to probe point definitions against minor code changes. For example, actual 10th line of schedule() can be moved easily by modifying schedule(), but the same line matching 'rq=cpu_rq*' may still exist in the function.) 244 The filter pattern is a glob matching pattern(s) to filter variables.
|
| /linux/tools/memory-model/scripts/ |
| H A D | parseargs.sh | 57 echo $1 needs argument $2 matching \"$5\"
|