Home
last modified time | relevance | path

Searched refs:nodes (Results 1 – 25 of 870) sorted by relevance

12345678910>>...35

/f-stack/freebsd/contrib/ipfilter/netinet/
H A Dradix_ipf.c125 nodes[0].addroff = nodes[0].addrkey + masklen;
126 nodes[0].maskoff = nodes[0].maskkey + masklen;
127 nodes[0].parent = &nodes[1];
131 nodes[1].left = &nodes[0];
407 if ((key[nodes[1].offset] & nodes[1].bitmask) == 0) {
410 nodes[1].right = &nodes[0];
1217 rnh->nodes[0].index, GNAME(rnh->nodes[0].parent),
1221 rnh->nodes[1].index, GNAME(rnh->nodes[1].parent),
1225 rnh->nodes[2].index, GNAME(rnh->nodes[2].parent),
1399 stp->nodes[0].parent = &stp->nodes[0];
[all …]
/f-stack/dpdk/drivers/common/dpaax/
H A Ddpaax_iova_table.c63 struct reg_node *nodes = NULL; in read_memory_node() local
128 if (!nodes) { in read_memory_node()
144 nodes[j].addr, nodes[j].len); in read_memory_node()
151 return nodes; in read_memory_node()
160 struct reg_node *nodes; in dpaax_iova_table_populate() local
177 if (nodes == NULL) { in dpaax_iova_table_populate()
185 tot_memory_size += nodes[i].len; in dpaax_iova_table_populate()
202 free(nodes); in dpaax_iova_table_populate()
228 entry[i].start = nodes[i].addr; in dpaax_iova_table_populate()
229 entry[i].len = nodes[i].len; in dpaax_iova_table_populate()
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/cpu/
H A Dcpu-topology.txt27 tree nodes.
44 nodes are listed.
62 - one or more cluster nodes or
114 A socket node's child nodes must be one or more cluster nodes.
123 nodes can be contained in parent cluster nodes.
131 - one or more core nodes
139 nodes are leaf nodes, otherwise they become containers of
140 thread nodes.
146 Properties for core nodes that are leaf nodes:
155 child nodes can be:
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/usb/
H A Dusb-device.txt7 Four types of device-tree nodes are defined: "host-controller nodes"
8 representing USB host controllers, "device nodes" representing USB devices,
9 "interface nodes" representing USB interfaces and "combined nodes"
20 Required properties for device nodes:
30 Required properties for device nodes with interface nodes:
35 Required properties for interface nodes:
49 Required properties for combined nodes:
59 Required properties for hub nodes with device nodes:
64 Required properties for host-controller nodes with device nodes:
/f-stack/app/redis-5.0.5/tests/cluster/
H A Dcluster.tcl9 set lines [split [R $id cluster nodes] "\r\n"]
10 set nodes {}
26 lappend nodes $node
28 return $nodes
38 set nodes [get_cluster_nodes $id]
39 foreach n $nodes {
48 set nodes [get_cluster_nodes $instance_id]
49 foreach n $nodes {
/f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/
H A Dmeson,pinctrl.txt21 === GPIO sub-nodes ===
26 Required properties for sub-nodes are:
35 === Other sub-nodes ===
37 Child nodes without the "gpio-controller" represent some desired
38 configuration for a pin or a group. Those nodes can be pinmux nodes or
39 configuration nodes.
41 Required properties for pinmux nodes are:
48 Required properties for configuration nodes:
51 Configuration nodes support the following generic properties, as
H A Dxlnx,zynq-pinctrl.txt12 Zynq's pin configuration nodes act as a container for an arbitrary number of
18 Each configuration node can consist of multiple nodes describing the pinmux and
19 pinconf options. Those nodes can be pinmux nodes or pinconf nodes.
24 Required properties for pinmux nodes are:
29 Required properties for configuration nodes:
H A Dpinctrl-bindings.txt21 for client device device tree nodes to map those state names to the pin
28 nodes. The decision to do this or not somewhat rests with the author of
48 node. These referenced pin configuration nodes must be child
49 nodes of the pin controller that they configure. Multiple
52 from multiple nodes for a single pin controller, each
55 pin configuration nodes.
109 globally for the pin controller or in child nodes for individual
112 Pin controller devices should contain the pin configuration nodes that client
131 The contents of each of those pin configuration child nodes is defined
136 The pin configuration nodes need not be direct children of the pin controller
[all …]
/f-stack/dpdk/doc/guides/prog_guide/
H A Dgraph_lib.rst22 - Support for out of tree nodes.
23 - Inbuilt nodes for packet processing.
122 Source nodes are static nodes created using ``RTE_NODE_REGISTER`` by passing
125 nodes will be called first. So that these nodes can be used as input nodes for a graph.
142 linking the N nodes.
167 This method enables the use case of Rx and Tx nodes where multiple of those nodes
171 ethdev nodes.
179 nodes or graph is not allowed.
260 Broadly speaking, there are two different types of nodes.
262 Static nodes
[all …]
H A Dtraffic_management.rst22 shared (by multiple nodes) shapers
24 drop, WRED, private (per node) and shared (by multiple nodes) WRED contexts
40 parameters such as maximum number of nodes, maximum number of hierarchical
78 limiters) for the hierarchy nodes, subject to the specific implementation
85 nodes.
125 management for a group of leaf nodes.
155 The TM hierarchical tree consists of leaf nodes and non-leaf nodes. Each leaf
160 is reserved for leaf nodes.
167 The children nodes with different priorities are scheduled using the SP
181 node and all the nodes that are subsequently added have to be added as
[all …]
/f-stack/dpdk/drivers/net/ipn3ke/
H A Dipn3ke_tm.c112 if (!nodes) in ipn3ke_hw_tm_init()
121 rte_free(nodes); in ipn3ke_hw_tm_init()
125 hw->nodes = nodes; in ipn3ke_hw_tm_init()
126 hw->port_nodes = nodes; in ipn3ke_hw_tm_init()
134 i++, nodes++) { in ipn3ke_hw_tm_init()
135 nodes->node_index = i; in ipn3ke_hw_tm_init()
141 nodes->weight = 0; in ipn3ke_hw_tm_init()
151 i++, nodes++) { in ipn3ke_hw_tm_init()
158 nodes->weight = 0; in ipn3ke_hw_tm_init()
168 i++, nodes++) { in ipn3ke_hw_tm_init()
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/pwm/
H A Dpwm-tipwmss.txt10 - address-cells: Specify the number of u32 entries needed in child nodes.
12 - size-cells: specify number of u32 entries needed to specify child nodes size
20 Also child nodes should also populated under PWMSS DT node.
33 /* child nodes go here */
46 /* child nodes go here */
57 /* child nodes go here */
/f-stack/freebsd/contrib/device-tree/Bindings/i2c/
H A Di2c-mux.txt4 numbered uniquely in a device dependent manner. The nodes for an i2c bus
15 For i2c multiplexers/switches that have child nodes that are a mixture
16 of both i2c child busses and other child nodes, the 'i2c-mux' subnode
25 Required properties for i2c child bus nodes:
30 Optional properties for i2c child bus nodes:
32 - Child nodes conforming to i2c bus binding
H A Di2c-fsi.txt9 nodes.
10 - #size-cells = <0>; : Number of size cells in child nodes.
11 - child nodes : Nodes to describe busses off the I2C
18 - child nodes : Nodes to describe devices on the I2C
/f-stack/dpdk/examples/server_node_efd/server/
H A Dargs.c84 parse_num_nodes(const char *nodes) in parse_num_nodes() argument
89 if (nodes == NULL || *nodes == '\0') in parse_num_nodes()
92 temp = strtoul(nodes, &end, 10); in parse_num_nodes()
H A Dinit.c56 struct node *nodes; variable
179 nodes = rte_malloc("node details", in init_shm_rings()
180 sizeof(*nodes) * num_nodes, 0); in init_shm_rings()
181 if (nodes == NULL) in init_shm_rings()
189 nodes[i].rx_q = rte_ring_create(q_name, in init_shm_rings()
192 if (nodes[i].rx_q == NULL) in init_shm_rings()
/f-stack/freebsd/contrib/device-tree/Bindings/media/
H A Dexynos4-fimc-is.txt30 The following are the FIMC-IS peripheral device nodes and can be specified
31 either standalone or as the fimc-is node child nodes.
33 i2c-isp (ISP I2C bus controller) nodes
44 For the above nodes it is required to specify a pinctrl state named "default",
47 Device tree nodes of the image sensors' controlled directly by the FIMC-IS
48 firmware must be child nodes of their corresponding ISP I2C bus controller node.
/f-stack/freebsd/contrib/device-tree/Bindings/net/
H A Dmarvell-pxa168.txt11 - #address-cells: must be 1 when using sub-nodes.
12 - #size-cells: must be 0 when using sub-nodes.
18 Sub-nodes:
21 Sub-nodes required properties:
/f-stack/freebsd/contrib/device-tree/Bindings/
H A Dgraph.txt10 There already is a simple directed graph between devices tree nodes using
11 phandle properties pointing to other nodes to describe connections that
30 Ports are described by child 'port' nodes contained in the device node.
37 and 'reg' properties is used to number the nodes.
66 All 'port' nodes can be grouped under an optional 'ports' node, which
68 nodes independently from any other child device nodes a device might
117 property present in the port and/or endpoint nodes then the following
/f-stack/app/redis-5.0.5/deps/jemalloc/test/unit/
H A Drb.c234 node_t nodes[NNODES]; in TEST_BEGIN() local
262 nodes[k].magic = NODE_MAGIC; in TEST_BEGIN()
263 nodes[k].key = bag[k]; in TEST_BEGIN()
268 tree_insert(&tree, &nodes[k]); in TEST_BEGIN()
289 tree_next(&tree, &nodes[k]); in TEST_BEGIN()
290 tree_prev(&tree, &nodes[k]); in TEST_BEGIN()
297 node_remove(&tree, &nodes[k], j - k); in TEST_BEGIN()
302 node_remove(&tree, &nodes[k-1], k); in TEST_BEGIN()
/f-stack/freebsd/netgraph/
H A DNOTES42 - Have a user level program to print out and manipulate nodes, etc.
49 command to list all existing nodes (in case you don't know the
53 - Need a way to get a list of ALL nodes.
57 - Enhance "netstat" to display all netgraph nodes -- or at least
58 all netgraph socket nodes.
68 - Need to implement passing meta information through socket nodes
77 - All nodes assume that all data mbufs have the M_PKTHDR flag set!
97 Every node has a queue, plus there is a list of nodes that have queued work.
/f-stack/freebsd/contrib/device-tree/Bindings/clock/
H A Dst,nomadik.txt23 PLL nodes: these nodes represent the two PLLs on the system,
27 Required properties for the two PLL nodes:
34 HCLK nodes: these represent the clock gates on individual
38 Requires properties for the HCLK nodes:
/f-stack/freebsd/contrib/device-tree/Bindings/display/ti/
H A Dti,omap4-dss.txt17 Required nodes:
20 Optional nodes:
54 Optional nodes:
70 Optional nodes:
91 Optional nodes:
114 Optional nodes:
/f-stack/freebsd/contrib/device-tree/Bindings/iio/
H A Diio-bindings.txt5 tree. Those nodes are designated as IIO providers. IIO consumer
6 nodes use a phandle and IIO specifier pair to connect IIO provider
17 #io-channel-cells: Number of cells in an IIO specifier; Typically 0 for nodes
18 with a single IIO output and 1 for nodes with multiple
65 Empty property indicating that child nodes can inherit named
66 IIO channels from this node. Useful for bus nodes to provide
/f-stack/app/redis-5.0.5/tests/support/
H A Dcluster.tcl37 proc redis_cluster {nodes} { argument
39 set ::redis_cluster::startup_nodes($id) $nodes
66 set nodes_descr [$r cluster nodes]
95 set nodes {} ; # addr -> node description hash.
123 dict set nodes $addr $node
134 set ::redis_cluster::nodes($id) $nodes
137 dict for {addr node} $nodes {
154 set nodes $::redis_cluster::nodes($id)
155 dict for {addr node} $nodes {

12345678910>>...35