| /kernel/linux/linux-5.10/net/netfilter/ipvs/ |
| D | Kconfig | 13 that will take care of intercepting incoming connections to a
52 reduce conflicts when there are hundreds of thousands of connections
61 not far less than the number of connections per second multiplying
63 virtual server gets 200 connections per second, the connection lasts
118 connections to different real servers in a round-robin manner.
127 connections to different real servers based on server weights
129 new connections first than those with less weights, and servers
130 with higher weights get more connections than those with less
131 weights and servers with equal weights get equal connections.
140 connections to the server with the least number of active
[all …]
|
| D | ip_vs_ovf.c | 8 * connections , will keep all connections to the node with the highest weight
9 * and overflow to the next node if the number of connections exceeds the node's
12 * active connections
33 * connections exceed weight in ip_vs_ovf_schedule()
|
| /kernel/linux/linux-4.19/net/netfilter/ipvs/ |
| D | Kconfig | 12 that will take care of intercepting incoming connections to a
52 reduce conflicts when there are hundreds of thousands of connections
61 not far less than the number of connections per second multiplying
63 virtual server gets 200 connections per second, the connection lasts
118 connections to different real servers in a round-robin manner.
127 connections to different real servers based on server weights
129 new connections first than those with less weights, and servers
130 with higher weights get more connections than those with less
131 weights and servers with equal weights get equal connections.
140 connections to the server with the least number of active
[all …]
|
| D | ip_vs_ovf.c | 12 * connections , will keep all conections to the node with the highest weight
13 * and overflow to the next node if the number of connections exceeds the node's
16 * active connections
38 * connections exceed weight in ip_vs_ovf_schedule()
|
| /kernel/linux/linux-5.10/sound/aoa/fabrics/ |
| D | layout.c | 23 /* These are the connections the layout fabric
57 struct codec_connection *connections; member
277 .connections = onyx_connections_noheadphones,
281 .connections = topaz_input,
288 .connections = onyx_connections_reallineout,
295 .connections = topaz_input,
303 .connections = onyx_connections_noheadphones,
310 .connections = topaz_input,
318 .connections = onyx_connections_noheadphones,
322 .connections = topaz_input,
[all …]
|
| /kernel/linux/linux-4.19/sound/aoa/fabrics/ |
| D | layout.c | 25 /* These are the connections the layout fabric
59 struct codec_connection *connections; member
279 .connections = onyx_connections_noheadphones,
283 .connections = topaz_input,
290 .connections = onyx_connections_reallineout,
297 .connections = topaz_input,
305 .connections = onyx_connections_noheadphones,
312 .connections = topaz_input,
320 .connections = onyx_connections_noheadphones,
324 .connections = topaz_input,
[all …]
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | ipvs-sysctl.txt | 28 Controls how ipvs will deal with connections that are detected
36 bit 1: enable rescheduling of new connections when it is safe.
41 bit 2: it is bit 1 plus, for TCP connections, when connections
51 connections handled by IPVS.
53 This should be enabled if connections handled by IPVS are to be
58 Connections handled by the IPVS FTP application module
99 memory for new connections. In the current code, the
134 detection) and add back the server later, and the connections
142 connections when its destination is not available.
152 subsequent otherwise persistent connections are sent to a
[all …]
|
| D | ip_dynaddr.txt | 3 This stuff allows diald ONESHOT connections to get established by
5 It is implemented for TCP diald-box connections(1) and IP_MASQuerading(2).
16 going up. So, the *same* (local AND masqueraded) connections requests that
|
| /kernel/linux/linux-4.19/drivers/platform/x86/ |
| D | intel_cht_int33fe.c | 38 struct device_connection connections[5]; member
178 data->connections[0].endpoint[0] = "port0"; in cht_int33fe_probe()
179 data->connections[0].endpoint[1] = "i2c-pi3usb30532"; in cht_int33fe_probe()
180 data->connections[0].id = "typec-switch"; in cht_int33fe_probe()
181 data->connections[1].endpoint[0] = "port0"; in cht_int33fe_probe()
182 data->connections[1].endpoint[1] = "i2c-pi3usb30532"; in cht_int33fe_probe()
183 data->connections[1].id = "typec-mux"; in cht_int33fe_probe()
184 data->connections[2].endpoint[0] = "port0"; in cht_int33fe_probe()
185 data->connections[2].endpoint[1] = "i2c-pi3usb30532"; in cht_int33fe_probe()
186 data->connections[2].id = "idff01m01"; in cht_int33fe_probe()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/driver-api/ |
| D | device_connection.rst | 2 Device connections
8 Devices often have connections to other devices that are outside of the direct
15 Device connections are generic descriptions of any type of connection between
18 Device connections alone do not create a dependency between the two devices.
27 Device connections should exist before device ``->probe`` callback is called for
28 either endpoint device in the description. If the connections are defined in
34 is needed if there are multiple connections between the two devices.
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | ipvs-sysctl.rst | 35 Controls how ipvs will deal with connections that are detected
43 bit 1: enable rescheduling of new connections when it is safe.
48 bit 2: it is bit 1 plus, for TCP connections, when connections
58 connections handled by IPVS.
60 This should be enabled if connections handled by IPVS are to be
65 Connections handled by the IPVS FTP application module
106 memory for new connections. In the current code, the
141 detection) and add back the server later, and the connections
149 connections when its destination is not available.
159 subsequent otherwise persistent connections are sent to a
[all …]
|
| D | ip_dynaddr.rst | 7 This stuff allows diald ONESHOT connections to get established by
9 It is implemented for TCP diald-box connections(1) and IP_MASQuerading(2).
21 going up. So, the *same* (local AND masqueraded) connections requests that
|
| /kernel/linux/linux-5.10/net/netfilter/ |
| D | xt_connlimit.c | 3 * connections per IP address.
6 * only ignore TIME_WAIT or gone connections
39 unsigned int connections; in connlimit_mt() local
72 connections = nf_conncount_count(net, info->data, key, tuple_ptr, in connlimit_mt()
74 if (connections == 0) in connlimit_mt()
78 return (connections > info->limit) ^ !!(info->flags & XT_CONNLIMIT_INVERT); in connlimit_mt()
134 MODULE_DESCRIPTION("Xtables: Number of connections matching");
|
| /kernel/linux/linux-4.19/net/netfilter/ |
| D | xt_connlimit.c | 3 * connections per IP address.
6 * only ignore TIME_WAIT or gone connections
37 unsigned int connections; in connlimit_mt() local
70 connections = nf_conncount_count(net, info->data, key, tuple_ptr, in connlimit_mt()
72 if (connections == 0) in connlimit_mt()
76 return (connections > info->limit) ^ !!(info->flags & XT_CONNLIMIT_INVERT); in connlimit_mt()
132 MODULE_DESCRIPTION("Xtables: Number of connections matching");
|
| /kernel/linux/linux-4.19/Documentation/blockdev/drbd/ |
| D | data-structure-v9.txt | 8 devices (aka volumes) and connections to other nodes ("peer nodes"). Each DRBD
27 volume number. Likewise, peer_devices can be accessed from connections by
29 linked lists. There are back pointers from peer_devices to their connections a
30 devices, and from connections and devices to their resource.
37 devices and connections; their lifetime is determined by the lifetime of the
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/blockdev/drbd/ |
| D | data-structure-v9.rst | 12 devices (aka volumes) and connections to other nodes ("peer nodes"). Each DRBD
31 volume number. Likewise, peer_devices can be accessed from connections by
33 linked lists. There are back pointers from peer_devices to their connections a
34 devices, and from connections and devices to their resource.
41 devices and connections; their lifetime is determined by the lifetime of the
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | coresight-cti.yaml | 18 The CTI component properties define the connections between the individual
28 described in the bindings as the actual connections are software
31 In general the connections between CTI and components via the trigger signals
35 In this case the ARM v8 architecture defines the required signal connections
45 on the connections between the CTI and other components for correct operation.
48 configuration). These registers may be used to explore the trigger connections
132 A trigger connections child node which describes the trigger signals
235 # v8 architecturally defined CTI - CPU + ETM connections generated by the
249 # Implementation defined CTI - CPU + ETM connections explicitly defined..
296 # Implementation defined CTI - non CoreSight component connections.
|
| /kernel/linux/linux-4.19/arch/um/drivers/ |
| D | port_kern.c | 27 struct list_head connections; member
63 list_add(&conn->list, &conn->port->connections); in pipe_interrupt()
71 "There are currently no UML consoles waiting for port connections.\n" \
198 .connections = LIST_HEAD_INIT(port->connections) }); in port_data()
239 conn = list_entry(port->connections.next, struct connection, in port_wait()
253 * connections until a good one is found. in port_wait()
|
| /kernel/linux/linux-5.10/arch/um/drivers/ |
| D | port_kern.c | 27 struct list_head connections; member
63 list_add(&conn->list, &conn->port->connections); in pipe_interrupt()
71 "There are currently no UML consoles waiting for port connections.\n" \
197 .connections = LIST_HEAD_INIT(port->connections) }); in port_data()
238 conn = list_entry(port->connections.next, struct connection, in port_wait()
252 * connections until a good one is found. in port_wait()
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | ip_vs.h | 168 /* thresholds for active connections */
178 __u32 conns; /* connections scheduled */
236 __u32 activeconns; /* active connections */
237 __u32 inactconns; /* inactive connections */
238 __u32 persistconns; /* persistent connections */
398 IPVS_DEST_ATTR_ACTIVE_CONNS, /* active connections */
399 IPVS_DEST_ATTR_INACT_CONNS, /* inactive connections */
400 IPVS_DEST_ATTR_PERSIST_CONNS, /* persistent connections */
447 IPVS_STATS_ATTR_CONNS, /* connections scheduled */
|
| /kernel/linux/linux-4.19/include/uapi/linux/ |
| D | ip_vs.h | 155 /* thresholds for active connections */
165 __u32 conns; /* connections scheduled */
223 __u32 activeconns; /* active connections */
224 __u32 inactconns; /* inactive connections */
225 __u32 persistconns; /* persistent connections */
385 IPVS_DEST_ATTR_ACTIVE_CONNS, /* active connections */
386 IPVS_DEST_ATTR_INACT_CONNS, /* inactive connections */
387 IPVS_DEST_ATTR_PERSIST_CONNS, /* persistent connections */
428 IPVS_STATS_ATTR_CONNS, /* connections scheduled */
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | coresight.h | 107 * @nr_inport: Number of elements for the input connections.
108 * @nr_outport: Number of elements for the output connections.
109 * @conns: Sparse array of nr_outport connections from this component.
172 * @pdata: Platform data with device connections associated to this device.
179 * @orphan: true if the component has connections that haven't been linked.
188 * path or connections.
190 * device. These will appear in the "connections" group.
191 * @has_conns_grp: Have added a "connections" group for sysfs links.
|
| /kernel/linux/linux-5.10/drivers/net/wan/ |
| D | Kconfig | 12 achievable with commonly used asynchronous modem connections.
120 Generic HDLC driver supporting raw HDLC over WAN connections.
129 over WAN connections.
139 Generic HDLC driver supporting Cisco HDLC over WAN connections.
147 Generic HDLC driver supporting Frame Relay over WAN connections.
155 Generic HDLC driver supporting PPP over WAN connections.
163 Generic HDLC driver supporting X.25 over WAN connections.
334 carry several logical point-to-point connections to other computers
350 How many logical point-to-point frame relay connections (the
|
| /kernel/linux/linux-5.10/Documentation/trace/coresight/ |
| D | coresight-ect.rst | 46 The hardware trigger connections between CTIs and devices is implementation
48 the connections have an architecturally defined standard layout.
76 connections subsystem triggers0 triggers1 uevent
84 * ``nr_trigger_cons`` : total connections - triggers<N> directories.
92 * ``connections``: Links to connected *CoreSight* devices. The number of
101 CoreSight and non-CoreSight connections.
195 channel / trigger connections using the appropriate sysfs attributes.
|
| /kernel/linux/linux-5.10/drivers/usb/serial/ |
| D | visor.h | 105 } connections[2]; member
129 * @num_ports: maximum number of functions/connections in use
132 * connections.end_point_info is non-zero. If value is 0, then
133 * connections.port contains the endpoint number, which is the same for in
142 * The maximum number of connections currently supported is 2
153 } connections[2]; member
|