Home
last modified time | relevance | path

Searched full:connections (Results 1 – 25 of 643) sorted by relevance

12345678910>>...26

/kernel/linux/linux-5.10/net/netfilter/ipvs/
DKconfig13 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 …]
Dip_vs_ovf.c8 * 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-5.10/sound/aoa/fabrics/
Dlayout.c23 /* 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-5.10/Documentation/networking/
Dipvs-sysctl.rst35 Controls how ipvs will deal with connections that are detected
42 bit 1: enable rescheduling of new connections when it is safe.
47 bit 2: it is bit 1 plus, for TCP connections, when connections
57 connections handled by IPVS.
59 This should be enabled if connections handled by IPVS are to be
64 Connections handled by the IPVS FTP application module
105 memory for new connections. In the current code, the
140 detection) and add back the server later, and the connections
148 connections when its destination is not available.
158 subsequent otherwise persistent connections are sent to a
[all …]
Dip_dynaddr.rst7 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/
Dxt_connlimit.c3 * 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");
DKconfig66 into connections.
100 connections. Typically they are copied to connections from
102 connections to packets with the same target, with the packets
114 connections using the same identity, as long as they are
172 tracking code will be able to do state tracking on DCCP connections.
186 tracking code will be able to do state tracking on SCTP connections.
197 connections.
220 Tracking FTP connections is problematic: special helpers are
313 - Blindly assumes that control connections are always established
325 data connections.
[all …]
Dnf_conncount.c3 * count the number of connections matching an arbitrary key.
11 * only ignore TIME_WAIT or gone connections
40 /* we will save the tuples of all connections we care about */
135 /* check the saved connections */ in __nf_conncount_add()
168 * we do not care about connections which are in __nf_conncount_add()
203 /* check the saved connections */ in nf_conncount_add()
245 * we do not care about connections which are in nf_conncount_gc_list()
624 MODULE_DESCRIPTION("netfilter: count number of connections matching a key");
/kernel/linux/linux-5.10/Documentation/admin-guide/blockdev/drbd/
Ddata-structure-v9.rst12 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/
Dcoresight-cti.yaml18 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-5.10/arch/um/drivers/
Dport_kern.c27 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/
Dip_vs.h168 /* 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-5.10/include/linux/
Dcoresight.h107 * @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/
DKconfig12 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/
Dcoresight-ect.rst46 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/
Dvisor.h105 } 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
/kernel/linux/linux-5.10/fs/hmdfs/comm/
Dconnection.c589 WRITE_ONCE(peer->sbi->connections.recent_ol, jif_tmp); in peer_online()
789 struct mutex *lock = &peer->sbi->connections.node_lock; in hmdfs_peer_release()
823 struct mutex *lock = &peer->sbi->connections.node_lock; in peer_put()
942 mutex_lock(&sbi->connections.node_lock); in hmdfs_connections_stop()
943 list_for_each_entry_safe(node, con_tmp, &sbi->connections.node_list, in hmdfs_connections_stop()
945 mutex_unlock(&sbi->connections.node_lock); in hmdfs_connections_stop()
948 mutex_lock(&sbi->connections.node_lock); in hmdfs_connections_stop()
950 mutex_unlock(&sbi->connections.node_lock); in hmdfs_connections_stop()
1002 mutex_lock(&sbi->connections.node_lock); in hmdfs_lookup_from_devid()
1003 list_for_each_entry(con, &sbi->connections.node_list, list) { in hmdfs_lookup_from_devid()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/
Dgraph.txt7 control flow to devices, but there can be more complex connections between
11 phandle properties pointing to other nodes to describe connections that
18 type of the connections, they just map their existence. Specific properties
24 the connecting data buses. A single port with multiple connections can
/kernel/linux/linux-5.10/drivers/greybus/
Dcore.c205 * Catch buggy drivers that fail to destroy their connections. in greybus_probe()
207 WARN_ON(!list_empty(&bundle->connections)); in greybus_probe()
237 * Disable (non-offloaded) connections early in case the interface is in greybus_remove()
241 list_for_each_entry(connection, &bundle->connections, bundle_links) { in greybus_remove()
253 /* Catch buggy drivers that fail to destroy their connections. */ in greybus_remove()
254 WARN_ON(!list_empty(&bundle->connections)); in greybus_remove()
/kernel/linux/linux-5.10/fs/hmdfs/
Dfile_root.c36 mutex_lock(&sbi->connections.node_lock); in get_next_con()
37 head = &sbi->connections.node_list; in get_next_con()
49 list_for_each_entry(con, &sbi->connections.node_list, list) { in get_next_con()
64 mutex_unlock(&sbi->connections.node_lock); in get_next_con()
Dmain.c329 mutex_lock(&sbi->connections.node_lock); in hmdfs_remote_statfs()
330 list_for_each_entry(con, &sbi->connections.node_list, list) { in hmdfs_remote_statfs()
333 mutex_unlock(&sbi->connections.node_lock); in hmdfs_remote_statfs()
340 mutex_lock(&sbi->connections.node_lock); in hmdfs_remote_statfs()
343 mutex_unlock(&sbi->connections.node_lock); in hmdfs_remote_statfs()
474 mutex_lock(&sbi->connections.node_lock); in hmdfs_sync_fs()
475 list_for_each_entry(con, &sbi->connections.node_list, list) { in hmdfs_sync_fs()
485 mutex_unlock(&sbi->connections.node_lock); in hmdfs_sync_fs()
500 mutex_lock(&sbi->connections.node_lock); in hmdfs_sync_fs()
510 mutex_lock(&sbi->connections.node_lock); in hmdfs_sync_fs()
[all …]
/kernel/linux/linux-5.10/net/netlabel/
Dnetlabel_unlabeled.h26 * incoming unlabeled connections.
45 * label for incoming unlabeled connections.
84 * label for incoming unlabeled connections.
102 * static label for incoming unlabeled connections.
/kernel/linux/linux-5.10/net/bluetooth/
DKconfig69 Bluetooth connections via 802.11 (wifi) physical layer
128 Bluetooth Low Energy Secure Connections feature.
135 legacy SMP as well as the Secure Connections features.
/kernel/linux/linux-5.10/net/ax25/
Dax25_ds_subr.c147 * A nasty problem arises if we count the number of DAMA connections
148 * wrong, especially when connections on the device already existed
150 * mode. We thus flag the 'real' slave connections with
152 * connections exist.
/kernel/linux/linux-5.10/net/lapb/
DKconfig15 currently supports LAPB only over Ethernet connections. If you want
16 to use LAPB connections over Ethernet, say Y here and to "LAPB over

12345678910>>...26