| /freebsd/contrib/llvm-project/lldb/source/Core/ |
| H A D | Communication.cpp | 1 //===-- Communication.cpp -------------------------------------------------===//
9 #include "lldb/Core/Communication.h"
29 Communication::Communication() in Communication() function in Communication
33 Communication::~Communication() { in ~Communication()
37 void Communication::Clear() { in Clear()
41 ConnectionStatus Communication::Connect(const char *url, Status *error_ptr) { in Connect()
44 LLDB_LOG(GetLog(LLDBLog::Communication), in Connect()
45 "{0} Communication::Connect (url = {1})", this, url); in Connect()
55 ConnectionStatus Communication::Disconnect(Status *error_ptr) { in Disconnect()
56 LLDB_LOG(GetLog(LLDBLog::Communication), "{0} Communication::Disconnect ()", in Disconnect()
[all …]
|
| H A D | ThreadedCommunication.cpp | 36 static constexpr llvm::StringLiteral class_name("lldb.communication"); in GetStaticBroadcasterClass()
41 : Communication(), Broadcaster(nullptr, name), m_read_thread_enabled(false), in ThreadedCommunication()
44 LLDB_LOG(GetLog(LLDBLog::Object | LLDBLog::Communication), in ThreadedCommunication()
59 LLDB_LOG(GetLog(LLDBLog::Object | LLDBLog::Communication), in ~ThreadedCommunication()
67 Communication::Clear(); in Clear()
73 return Communication::Disconnect(error_ptr); in Disconnect()
80 Log *log = GetLog(LLDBLog::Communication); in Read()
155 return Communication::Read(dst, dst_len, timeout, status, error_ptr); in Read()
167 LLDB_LOG(GetLog(LLDBLog::Communication), in StartReadThread()
200 LLDB_LOG(GetLog(LLDBLog::Communication), in StopReadThread()
[all …]
|
| /freebsd/sys/contrib/ena-com/ |
| H A D | ena_com.h | 470 * @ena_dev: ENA communication layer struct
481 * @ena_dev: ENA communication layer struct
488 * @ena_dev: ENA communication layer struct
495 * @ena_dev: ENA communication layer struct
503 * @ena_dev: ENA communication layer struct
508 * @ena_dev: ENA communication layer struct
515 * @ena_dev: ENA communication layer struct
522 * @ena_dev: ENA communication layer struct
530 * @ena_dev: ENA communication layer struct
535 * @ena_dev: ENA communication layer struct
[all …]
|
| /freebsd/contrib/ofed/librdmacm/man/ |
| H A D | rdma_create_id.3 | 4 rdma_create_id \- Allocate a communication identifier.
15 The communication channel that events associated with the
18 A reference where the allocated communication identifier will be
25 Creates an identifier that is used to track communication information.
31 communication. The difference is that RDMA communication requires
32 explicitly binding to a specified RDMA device before communication
34 communication events on an rdma_cm_id are reported through the associated
46 Provides reliable, connection-oriented QP communication. Unlike TCP, the RDMA
47 port space provides message, not stream, based communication.
49 Provides unreliable, connectionless QP communication. Supports both datagram
[all …]
|
| H A D | rdma_cm.7 | 4 rdma_cm \- RDMA communication manager.
8 Used to establish communication over RDMA transports.
10 The RDMA CM is a communication manager used to setup reliable, connected
14 communication must be over a specific RDMA device, and data transfers
17 The RDMA CM can control both the QP and communication management (connection setup /
18 teardown) portions of an RDMA API, or only the communication management
66 or client, side of communication. This flow assume asynchronous operation with
87 allocate a QP for the communication
116 communication between nodes. No actual connection is formed between QPs
123 or server, side of communication. A general connection flow would be:
[all …]
|
| H A D | udaddy.1 | 14 Establishes a set of unreliable RDMA datagram communication paths between two
16 then tears down the communication.
21 communication. The used name or address must route over an RDMA device.
29 The number of communication paths to establish between the client and server.
30 The test uses unreliable datagram communication, so no actual connections are
42 Indicates the type of service used for the communication. Type of service
46 The port space of the datagram communication. May be either the RDMA
|
| H A D | rdma_migrate_id.3 | 4 rdma_migrate_id \- Move a communication identifier to a different event channel.
13 An existing communication identifier to migrate.
15 The communication channel that events associated with the
18 Migrates a communication identifier to a different event channel.
23 This routine migrates a communication identifier to the specified event
|
| H A D | rdma_xserver.1 | 4 rdma_xserver \- RDMA CM communication server test program
11 Uses the librdmacm to establish various forms of communication and exchange
19 \-c communication type
20 Specifies the type of communication established with the client program. 'r'
|
| H A D | rdma_get_cm_event.3 | 4 rdma_get_cm_event \- Retrieves the next pending communication event.
15 Allocated information about the next communication event.
17 Retrieves a communication event. If no events are pending, by default,
29 Communication event details are returned in the rdma_cm_event structure.
36 communication.
41 Specifies the type of communication event which occurred. See EVENT TYPES
113 The following types of communication events may be reported.
|
| /freebsd/contrib/llvm-project/lldb/include/lldb/Core/ |
| H A D | Communication.h | 1 //===-- Communication.h -----------------------------------------*- C++ -*-===//
26 /// \class Communication Communication.h "lldb/Core/Communication.h" An
29 /// Communication is an class that handles data communication between two data
30 /// sources. It uses a Connection class to do the real communication. This
39 class Communication {
41 /// Construct the Communication object.
42 Communication();
47 virtual ~Communication();
63 /// \see Status& Communication::GetError ();
74 /// \see Status& Communication::GetError ();
[all …]
|
| H A D | ThreadedCommunication.h | 12 #include "lldb/Core/Communication.h"
26 /// "lldb/Core/ThreadedCommunication.h" Variation of Communication that
29 /// ThreadedCommunication enhances the base Communication class with support
39 /// size_t Communication::ReadFromConnection (void *, size_t, uint32_t);
43 /// want packet based communication should override AppendBytesToCache. The
61 class ThreadedCommunication : public Communication, public Broadcaster {
62 using Communication::Communication;
109 /// \see Status& Communication::GetError ();
145 /// By making a communication class that uses different connections it
146 /// allows a single communication interface to negotiate and change its
[all …]
|
| /freebsd/share/doc/psd/20.ipctut/ |
| H A D | tutor.me | 36 Interprocess Communication Tutorial
54 Berkeley UNIX\(dg 4.4BSD offers several choices for interprocess communication.
60 and the use of datagram and stream communication. The intent of this
72 Facilities for interprocess communication (IPC) and networking
80 or to communication channels.
96 The use of descriptors is not the only communication interface
104 as a means of interprocess communication.
129 processes and interprocess communication.
131 communication that are supported by Berkeley UNIX 4.4BSD.
134 channels of communication.
[all …]
|
| /freebsd/contrib/ofed/librdmacm/ |
| H A D | rdma_cma.h | 201 * rdma_create_event_channel - Open a channel used to report communication events.
215 * rdma_destroy_event_channel - Close an event communication channel.
216 * @channel: The communication channel to destroy.
229 * rdma_create_id - Allocate a communication identifier.
230 * @channel: The communication channel that events associated with the
232 * @id: A reference where the allocated communication identifier will be
237 * Creates an identifier that is used to track communication information.
240 * communication. The difference is that RDMA communication requires
241 * explicitly binding to a specified RDMA device before communication
242 * can occur, and most operations are asynchronous in nature. Communication
[all …]
|
| /freebsd/share/doc/psd/05.sysman/ |
| H A D | 2.3.t | 30 Interprocess communication primitives
32 Communication domains
35 communication \fIdomains\fP. A communication domain
39 domain, AF_UNIX, for communication within the system, the ``Internet''
40 domain for communication in the DARPA Internet, AF_INET,
41 and the ``NS'' domain, AF_NS, for communication
47 Within a domain, communication takes place between communication endpoints
52 abstract type, which describes the semantics of communication using that
65 The SOCK_DGRAM type models the semantics of datagrams in network communication:
76 Connection setup is required before data communication may begin.
[all …]
|
| /freebsd/share/doc/psd/21.ipc/ |
| H A D | 2.t | 44 The basic building block for communication is the \fIsocket\fP.
45 A socket is an endpoint of communication to which a name may
48 \fIcommunication domains\fP.
49 A communication domain is an
53 example, in the UNIX communication domain sockets are
60 4.4BSD IPC facilities support four separate communication domains:
61 the UNIX domain, for on-system communication;
64 using the Internet standard communication protocols;
66 communicate using the Xerox standard communication
74 The underlying communication
[all …]
|
| H A D | 1.t | 44 communication.
54 The BSD interprocess communication
58 communication. Prior to the 4BSD facilities, the only
80 to users. Further, the communication facilities
94 of communication. Section 3 describes some of the supporting
|
| H A D | 0.t | 39 An Advanced 4.4BSD Interprocess Communication Tutorial
76 communication facilities included in the
81 It discusses the overall model for interprocess communication
82 and introduces the interprocess communication primitives
|
| /freebsd/contrib/llvm-project/lldb/include/lldb/Utility/ |
| H A D | Connection.h | 31 /// A communication connection class.
33 /// A class that implements that actual communication functions for
35 /// available from a two way communication connection.
37 /// This class is designed to only do very simple communication functions.
38 /// Instances can be instantiated and given to a Communication class to
47 /// Communication object.
66 /// \see Status& Communication::GetError ();
82 /// \see Status& Communication::GetError ();
117 /// \see size_t Communication::Read (void *, size_t, uint32_t);
|
| /freebsd/sys/ofed/include/rdma/ |
| H A D | ib_cm.h | 301 * ib_cm_handler - User-defined callback to process communication events.
302 * @cm_id: Communication identifier associated with the reported event.
303 * @event: Information about the communication event.
305 * IB_CM_REQ_RECEIVED and IB_CM_SIDR_REQ_RECEIVED communication events
310 * to a user's existing communication identifier.
313 * however, returning a non-zero value instructs the communication manager to
333 * ib_create_cm_id - Allocate a communication identifier.
334 * @device: Device associated with the cm_id. All related communication will
337 * @context: User specified context associated with the communication
340 * Communication identifiers are used to track connection states, service
[all …]
|
| H A D | rdma_cm.h | 247 * @id: Communication identifier associated with the QP attributes to
313 * communication events. Events that should be reported to the CM and
336 * @id: Communication identifier associated with the request.
355 * @id: Communication identifier to associated with service type.
360 * performing route resolution, as existing communication on the
369 * @id: Communication identifier to configure.
379 * @id: Communication identifer to configure.
389 * @id: Communication identifier associated with the address.
396 * @id: Communication identifier that received the REJECT event.
|
| /freebsd/lib/libsys/ |
| H A D | socket.2 | 33 .Nd create an endpoint for communication
44 creates an endpoint for communication and returns a descriptor.
49 communication will take place; this selects the protocol family
81 which specifies the semantics of communication.
138 .Dq "communication domain"
139 in which communication
305 .%T "An Introductory 4.3 BSD Interprocess Communication Tutorial"
310 .%T "BSD Interprocess Communication Tutorial"
|
| /freebsd/share/man/man4/ |
| H A D | vmci.4 | 9 .Nd VMware Virtual Machine Communication Interface
27 driver provides support for the VMware Virtual Machine Communication Interface
46 The primary communication mechanisms supported are a point-to-point
52 events related to the state of the VMCI communication channels, and the
|
| /freebsd/stand/efi/include/Protocol/ |
| H A D | Ip4Config2.h | 36 /// The interface information of the communication device this EFI
44 /// running on the communication device this EFI IPv4
61 /// stack running on the communication device this EFI IPv4
72 /// the communication device this EFI IPv4 Configuration II
167 Set the configuration for the EFI IPv4 network stack running on the communication device this EFI
171 running on the communication device this EFI IPv4 Configuration II Protocol instance manages.
217 Get the configuration data for the EFI IPv4 network stack running on the communication device this
221 running on the communication device this EFI IPv4 Configuration II Protocol instance manages.
310 /// An EFI IPv4 Configuration II Protocol instance will be installed on each communication device t…
|
| /freebsd/sys/contrib/device-tree/Bindings/mailbox/ |
| H A D | ti,omap-mailbox.yaml | 13 The OMAP Mailbox hardware facilitates communication between different
16 interconnect bus. The communication is achieved through a set of registers
27 h/w fifo. Communication between different processors is achieved through the
49 within a SoC. The sub-mailboxes (actual communication channels) are
59 phandle to the intended sub-mailbox child node to be used for communication.
61 communication channel to be used by the client user.
68 uni-directional communication channel. A typical sub-mailbox device uses
90 node and represents the actual communication channel used to send and
|
| /freebsd/sys/contrib/device-tree/Bindings/iio/ |
| H A D | sensorhub.txt | 9 - interrupts: communication interrupt
10 - ap-mcu-gpios: [out] ap to sensorhub line - used during communication
11 - mcu-ap-gpios: [in] sensorhub to ap - used during communication
|