Home
last modified time | relevance | path

Searched full:established (Results 1 – 25 of 662) sorted by relevance

12345678910>>...27

/openbmc/bmcweb/redfish-core/include/registries/
H A Dfabric_message_registry.hpp172 … "Indicates that a switch's downstream connection is established but is in a degraded state.",
173 … "Switch '%1' downstream link is established on port '%2', but is running in a degraded state.",
185 … "Indicates that a switch's interswitch connection is established but is in a degraded state.",
186 … "Switch '%1' interswitch link is established on port '%2', but is running in a degraded state.",
198 … "Indicates that a switch's upstream connection is established but is in a degraded state.",
199 … "Switch '%1' upstream link is established on port '%2', but is running in a degraded state.",
224 "Indicates that a switch's downstream connection is established.",
225 "Switch '%1' downstream link is established on port '%2'.",
238 …"Switch '%1' downstream link on port '%2' was established and dropped %3 times in the last %4 minu…
304 "Indicates that a switch's interswitch connection is established.",
[all …]
H A Dnetwork_device_message_registry.hpp82 "Indicates that a network connection was established.",
83 … "A network connection was established for network adapter '%1' port '%2' function '%3'.",
96 … "Indicates that a network connection was established, but at an unexpectedly low link speed.",
97 … "A degraded network connection was established for network adapter '%1' port '%2' function '%3'.",
111 …etwork connection for network adapter '%1' port '%2' function '%3' was established and dropped '%4…
/openbmc/linux/tools/testing/selftests/netfilter/
H A Dconntrack_icmp_related.sh15 # nat of "established" icmp-echo "connection".
140 meta l4proto { icmp, icmpv6 } ct state new,established accept
159 meta l4proto { icmp, icmpv6 } ct state established,untracked accept
171 counter established { }
175 meta l4proto { icmp, icmpv6 } ct state established,untracked accept
178 meta l4proto { icmp, icmpv6 } ct state "established" counter name "established" accept
183 meta l4proto { icmp, icmpv6 } ct state established,untracked accept
186 meta l4proto { icmp, icmpv6 } ct state "established" counter name "established"
/openbmc/linux/drivers/tty/hvc/
H A Dhvsi_lib.c23 pv->established = 0; in hvsi_start_handshake()
39 pv->established = 0; in hvsi_send_close()
105 pv->established = 1; in hvsi_got_query()
224 if (!pv->established) { in hvsilib_get_chars()
277 if (!pv->established) in hvsilib_read_mctrl()
322 if (pv->established) in hvsilib_establish()
323 goto established; in hvsilib_establish()
345 if (pv->established) in hvsilib_establish()
346 goto established; in hvsilib_establish()
351 if (!pv->established) { in hvsilib_establish()
[all …]
/openbmc/linux/tools/testing/selftests/bpf/progs/
H A Dcgroup_tcp_skb.c74 g_sock_state = ESTABLISHED; in ingress_accept()
103 g_sock_state = ESTABLISHED; in ingress_connect()
114 case ESTABLISHED: in egress_close_remote()
138 case ESTABLISHED: in ingress_close_remote()
159 case ESTABLISHED: in egress_close_local()
179 case ESTABLISHED: in ingress_close_local()
/openbmc/openbmc-test-automation/bin/
H A Dwebsocket_monitor.py140 websocket_obj The websocket established during opne_socket().
169 websocket_obj The websocket established during opne_socket().
185 websocket_obj The websocket established during opne_socket().
197 websocket_obj The websocket established during opne_socket().
/openbmc/linux/drivers/infiniband/ulp/rtrs/
H A DREADME27 An established connection between a client and a server is called rtrs
42 On an established session client sends to server write or read messages.
69 established. They are used by the server to find a persisting session/path or
84 3. After all connections of a path are established client sends to server the
92 5. Session becomes connected after all paths to be established are connected
108 *after all connections are established:
/openbmc/linux/drivers/hwmon/occ/
H A DKconfig15 established through I2C bus.
29 established through SBE fifo on an FSI bus.
/openbmc/linux/include/net/netfilter/
H A Dnf_tproxy.h63 * - match: if there's a fully established connection matching the
66 * established connection
79 * belonging to established connections going through that one.
/openbmc/linux/Documentation/networking/
H A Dip_dynaddr.rst7 This stuff allows diald ONESHOT connections to get established by
22 bring the link up will be able to get established.
H A Dx25-iface.rst36 Establish the LAPB link. If the link is already established then the connect
59 LAPB link has been established. The same message is used for both a LAPB
/openbmc/u-boot/arch/arm/mach-tegra/
H A Divc.c24 * The transmitting end can enter the established state from the sync or
26 * established state, indicating that has cleared the counters in our
43 * return to the established state once it has cleared its counters.
423 * Move to ESTABLISHED state. We know that the remote end has in tegra_ivc_channel_notified()
438 * the ACK or ESTABLISHED state. Next, order observation of in tegra_ivc_channel_notified()
444 * Move to ESTABLISHED state. We know that we have previously in tegra_ivc_channel_notified()
460 * channel is already fully established, or we are waiting for in tegra_ivc_channel_notified()
/openbmc/openbmc/poky/documentation/sdk-manual/
H A Dworking-projects.rst140 To learn about environment variables established when you run the
164 environment variables established when you run the cross-toolchain
208 In a new shell environment variables are not established for the SDK
221 established through the script::
316 the compiler used was the compiler established through the :term:`CC`
341 established SDK compiler. However, when you run ``make``, use a
/openbmc/linux/net/netfilter/
H A Dxt_TPROXY.c49 * and the current packet belongs to an already established in tproxy_tg4()
65 /* no, there's no established connection, check if in tproxy_tg4()
126 * and the current packet belongs to an already established in tproxy_tg6_v1()
147 /* no there's no established connection, check if in tproxy_tg6_v1()
H A Dnft_tproxy.c47 * belongs to an already established connection in nft_tproxy_eval_v4()
68 /* no, there's no established connection, check if in nft_tproxy_eval_v4()
115 * belongs to an already established connection in nft_tproxy_eval_v6()
140 /* no there's no established connection, check if in nft_tproxy_eval_v6()
/openbmc/linux/drivers/infiniband/core/
H A Diwcm.c122 * ACTIVE IDS: 4: CONNECT_REPLY, ESTABLISHED, DISCONNECT, CLOSE
123 * PASSIVE IDS: 3: ESTABLISHED, DISCONNECT, CLOSE
299 * - If we are ESTABLISHED, move to CLOSING and modify the QP state
638 * CM_ID <-- ESTABLISHED
640 * Accepts an inbound connection request and generates an ESTABLISHED
642 * until the ESTABLISHED event is received from the provider.
843 * Passive Side: CM_ID <-- ESTABLISHED
845 * The provider generated an ESTABLISHED event which means that
850 * remote peer closed, the ESTABLISHED event would be received followed
878 * Active Side: CM_ID <-- ESTABLISHED
[all …]
/openbmc/linux/arch/powerpc/include/asm/
H A Dhvsi.h70 unsigned int established:1; /* protocol established */ member
/openbmc/linux/drivers/firmware/tegra/
H A Divc.c22 * The transmitting end can enter the established state from the sync or
24 * established state, indicating that has cleared the counters in our
41 * return to the established state once it has cleared its counters.
504 * Move to ESTABLISHED state. We know that the remote end has in tegra_ivc_notified()
521 * the ACK or ESTABLISHED state. Next, order observation of in tegra_ivc_notified()
527 * Move to ESTABLISHED state. We know that we have previously in tegra_ivc_notified()
543 * channel is already fully established, or we are waiting for in tegra_ivc_notified()
/openbmc/linux/tools/testing/selftests/bpf/prog_tests/
H A Dbpf_iter_setsockopt.c83 if (!ASSERT_EQ(i, nr_est, "create established fds")) { in make_established()
126 if (!ASSERT_OK_PTR(est_fds, "create established")) in do_bpf_iter_setsockopt()
164 /* Check established fds for dctcp */ in do_bpf_iter_setsockopt()
/openbmc/ipmitool/src/plugins/lanplus/
H A DREADME.sol17 established on a port different than the RMCP+ port that the "activate
20 Once a session has been established (the activate payload command
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DOutboundConnection.v1_0_2.json203 …ent and shall close the connection if one is already established. When a connection is establishe…
311 …onnection if the connection is dropped or not established. If the connection is dropped or not es…
312 …l set the `ConnectionEnabled` property to `false`. If a connection is established, the service sh…
H A DManagerNetworkProtocol.v1_10_1.json210 …he default `Port` property value should be `21` for compatibility with established client implemen…
216 … the manager. The default value should be `21` for compatibility with established client implemen…
222 …he default `Port` property value should be `80` for compatibility with established client implemen…
227 …e default `Port` property value should be `443` for compatibility with established client implemen…
241 …e default `Port` property value should be `623` for compatibility with established client implemen…
288 … the manager. The default value should be `22` for compatibility with established client implemen…
294 …e default `Port` property value should be `161` for compatibility with established client implemen…
299 … default `Port` property value should be `1900` for compatibility with established client implemen…
304 … the manager. The default value should be `22` for compatibility with established client implemen…
314 …he default `Port` property value should be `23` for compatibility with established client implemen…
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DManagerNetworkProtocol.v1_10_1.json210 …he default `Port` property value should be `21` for compatibility with established client implemen…
216 … the manager. The default value should be `21` for compatibility with established client implemen…
222 …he default `Port` property value should be `80` for compatibility with established client implemen…
227 …e default `Port` property value should be `443` for compatibility with established client implemen…
241 …e default `Port` property value should be `623` for compatibility with established client implemen…
288 … the manager. The default value should be `22` for compatibility with established client implemen…
294 …e default `Port` property value should be `161` for compatibility with established client implemen…
299 … default `Port` property value should be `1900` for compatibility with established client implemen…
304 … the manager. The default value should be `22` for compatibility with established client implemen…
314 …he default `Port` property value should be `23` for compatibility with established client implemen…
/openbmc/qemu/net/
H A Dutil.h73 /* states < TCPS_ESTABLISHED are those where connections not established */
74 #define TCPS_ESTABLISHED 4 /* established */
/openbmc/qemu/include/io/
H A Dchannel-socket.h91 * execution control until the connection is established or
132 * execution control until the connection is established or
178 * is established or an error occurs.

12345678910>>...27