Searched full:message (Results 1 – 25 of 469) sorted by relevance
12345678910>>...19
3 Message Queues5 Message queue is a simple low-capacity IPC channel between two virtual machines.7 message queue is unidirectional and buffered in the hypervisor. A full-duplex10 The size of the queue and the maximum size of the message that can be passed is11 fixed at creation of the message queue. Resource manager is presently the only12 use case for message queues, and creates messages queues between itself and VMs13 with a fixed maximum message size of 240 bytes. Longer messages require a14 further protocol on top of the message queue messages themselves. For instance,18 The diagram below shows how message queue works. A typical configuration19 involves 2 message queues. Message queue 1 allows VM_A to send messages to VM_B.[all …]
11 - Message lock26 Message lock29 SoundWire message transfer lock. This mutex is part of30 Bus data structure (sdw_bus). This lock is used to serialize the message38 Message transfer.40 1. For every message transfer42 a. Acquire Message lock.44 b. Transfer message (Read/Write) to Slave1 or broadcast message on47 c. Release Message lock59 <-------------------------------+ a. Acquire Message lock[all …]
1 What: /sys/kernel/debug/scmi/<n>/raw/message5 Description: SCMI Raw synchronous message injection/snooping facility; write6 a complete SCMI synchronous command message (header included)12 and sent while the replies are read back one message at time13 (receiving an EOF at each message boundary).20 Description: SCMI Raw asynchronous message injection/snooping facility; write21 a complete SCMI asynchronous command message (header included)30 and sent while the replies are read back one message at time31 (receiving an EOF at each message boundary).38 Description: SCMI Raw message errors facility; any kind of timed-out or[all …]
9 the user can send a message to the target to start failing read93 $ sudo dmsetup message dust1 0 addbadblock 6096 $ sudo dmsetup message dust1 0 addbadblock 6799 $ sudo dmsetup message dust1 0 addbadblock 72111 To enable the "fail read on bad block" behavior, send the "enable" message::113 $ sudo dmsetup message dust1 0 enable144 result in an "Invalid argument" error, as well as a helpful message::146 $ sudo dmsetup message dust1 0 addbadblock 88147 device-mapper: message ioctl on dust1 failed: Invalid argument151 result in an "Invalid argument" error, as well as a helpful message::[all …]
42 Since MCTP is message-based, only ``SOCK_DGRAM`` sockets are supported.99 match the network, address, and message type will be received by this socket.101 messages with the TO bit set, to indicate an incoming request message, rather118 The ``smctp_type`` field specifies which message types to receive. Only the121 receiving packets with and without a message integrity check footer.123 ``sendto()``, ``sendmsg()``, ``send()`` : transmit an MCTP message126 An MCTP message is transmitted using one of the ``sendto()``, ``sendmsg()`` or135 /* set message destination */142 /* arbitrary message to send, with message-type header */152 EID. If ``MCTP_TAG_OWNER`` is not set, the message will be sent with the tag[all …]
25 outside source. Message are parsed and delivered as the sequence is36 that is called when a full message has been completed.56 Temporarily pause a stream parser. Message parsing is suspended92 parser will parse. timeo is timeout for completing a message.102 buffer and message timeout is the receive timeout for the socket.121 parse_msg is called to determine the length of the next message124 next application layer message in the stream.128 where the message starts in the skb.133 >0 indicates length of successfully parsed message134 0 indicates more data must be received to parse the message[all …]
7 The design of the network interface message level setting.12 The design of the debugging message interface was guided and18 integer variable that controls the debug message level. The message21 The message level was not precisely defined past level 3, but were34 Initially this message level variable was uniquely named in each driver45 - Per-interface rather than per-driver message level setting.76 The set of message levels is named
7 Kernel Connection Multiplexor (KCM) is a mechanism that provides a message based45 The multiplexor provides the message steering. In the transmit path, messages70 Message delineation73 Messages are sent over a TCP stream with some application protocol message75 of a received message can be deduced from the application protocol header78 A TCP stream must be parsed to determine message boundaries. Berkeley Packet81 a new message and is given an skbuff that contains the bytes received so far.82 It parses the message header and returns the length of the message. Given this83 information, KCM will construct the message of the stated length and deliver it98 KCM limits the maximum receive message size to be the size of the receive[all …]
15 def warn(app, message): argument16 logger.warning(message)18 def verbose(app, message): argument19 logger.verbose(message)21 def info(app, message): argument22 logger.info(message)
71 [OUTER NEST OR MESSAGE LEVEL]84 the wrapper attr has very similar characteristics to a netlink message. It may87 a sub-message.89 A sub-message attribute uses the value of another attribute as a selector key to90 choose the right sub-message format. For example if the following attribute has103 type: sub-message104 sub-message: linkinfo-data-msg107 Then we look for a sub-message definition called ``linkinfo-data-msg`` and use109 correct format for the sub-message:126 This would decode the attribute value as a sub-message with the attribute-set[all …]
1 * FSL MPIC Message Registers4 representation of the message register blocks found in some FSL MPIC9 - compatible: Specifies the compatibility list for the message register12 the MPIC containing the message registers.15 message register block's addressable register space. The type shall be27 bit at bit 'n' indicates that message register 'n' can receive interrupts.29 be <u32>. If not present, then all of the message registers in the block34 An alias should be created for every message register block. They are not50 // Message registers 0 and 2 in this block can receive interrupts on59 // Message registers 0 and 2 in this block can receive interrupts on
15 message envelopes may match, the pair that includes the earliest posted-send21 When a message is sent from the sender to the receiver, the communication24 this is an expected message, otherwise it is called an unexpected message.31 1. The Eager protocol- the complete message is sent when the send is39 A fin message needs to be received in order for the buffer to be reused.45 unexpected message list. The application posts receive buffers through calls51 pre-posted receive for this arriving message, it is passed to the software and52 placed in the unexpected message list. Otherwise the match is processed,57 When a receive-message is posted, the communication library will first check58 the software unexpected message list for a matching receive. If a match is[all …]
14 CEC_RECEIVE, CEC_TRANSMIT - Receive or transmit a CEC message39 To receive a CEC message the application has to fill in the45 is non-zero and no message arrived within ``timeout`` milliseconds, then48 A received message can be:50 1. a message received from another CEC device (the ``sequence`` field will58 To send a CEC message the application has to fill in the struct72 the reply will arrive in a later message. The ``sequence`` field can102 - Timestamp in ns of when the last byte of the message was transmitted.107 - Timestamp in ns of when the last byte of the message was received.112 - The length of the message. For :ref:`ioctl CEC_TRANSMIT <CEC_TRANSMIT>` this is filled in[all …]
45 # <op>[,<mode>] rx-nack NACK the message instead of sending an ACK47 # <op>[,<mode>] rx-add-byte add a spurious byte to the received CEC message48 # <op>[,<mode>] rx-remove-byte remove the last byte from the received CEC message49 # any[,<mode>] rx-arb-lost [<poll>] generate a POLL message to trigger an arbitration lost60 # <op>[,<mode>] tx-add-bytes <num> append <num> (1-255) spurious bytes to the message61 # <op>[,<mode>] tx-remove-byte drop the last byte from the message71 # <op> CEC message opcode (0-255) or 'any'73 # <bit> CEC message bit (0-159)75 # <poll> CEC poll message used to test arbitration lost (0x00-0xff, default 0x0f)101 received or transmitted message, ``always`` to always trigger the error[all …]
47 When a CEC message is received, then the CEC framework will decide how48 it will be processed. If the message is a reply to an earlier49 transmitted message, then the reply is sent back to the filehandle that52 If the message is not a reply, then the CEC framework will process it53 first. If there is no follower, then the message is just discarded and a55 process it. If there is a follower, then the message is passed on to the57 the new message. The framework expects the follower to make the right198 Core message processing details:204 .. flat-table:: Core Message Processing215 does nothing and this message has to be handled by a follower[all …]
57 2.2 Message passing locks62 managed through three locks: "token", "message", and "ack", together63 with the Lock Value Block (LVB) of one of the "message" lock.76 other nodes to acknowledge the message before proceeding. Only one77 message can be processed at a time.79 3.1 Message Types96 RESYNCING message identifies a range of the devices that the105 the array. Message contains an identifier for that device. See112 array. The slot-number of the device is included in the message.137 3.2.2 message[all …]
12 When the driver receives a special netlink message with the appropriate40 callback function which will be called when a message with above idx.val71 msg->seq and msg->ack are used to determine message genealogy. When72 someone sends a message, they use a locally unique sequence and random76 The sequence number is incremented with each message sent.78 If you expect a reply to the message, then the sequence number in the79 received message MUST be the same as in the original message, and the82 If we receive a message and its sequence number is not equal to one we83 are expecting, then it is a new message. If we receive a message and86 message + 1, then it is a new message.[all …]
1 Message-based devices4 Fusion message devices7 .. kernel-doc:: drivers/message/fusion/mptbase.c10 .. kernel-doc:: drivers/message/fusion/mptscsih.c
1 Message Digest Algorithm Definitions5 :doc: Message Digest Algorithm Definitions10 Asynchronous Message Digest API14 :doc: Asynchronous Message Digest API28 Synchronous Message Digest API32 :doc: Synchronous Message Digest API
1 Texas Instruments' Message Manager Driver4 The Texas Instruments' Message Manager is a mailbox controller that has5 configurable queues selectable at SoC(System on Chip) integration. The Message10 Message Manager Device Node:14 - compatible: Shall be: "ti,k2g-message-manager"24 For ti,k2g-message-manager, this shall contain:33 compatible = "ti,k2g-message-manager";
19 write functions behave a bit differently because the message formats26 HCI messages consist of an eight bit header and the message body. The27 header contains the message length. Maximum size for an HCI message is30 and third (LSB) bytes of the message. The maximum FW message length is
24 - description: message RAM55 Message RAM configuration data.56 Multiple M_CAN instances can share the same Message RAM58 in Message RAM is also configurable, so this property is59 telling driver how the shared or private Message RAM are64 The 'offset' is an address offset of the Message RAM where66 0x0 if you're using a private Message RAM. The remain cells78 Please refer to 2.4.1 Message RAM Configuration in Bosch82 - description: The 'offset' is an address offset of the Message RAM where84 you're using a private Message RAM.
15 of the message queues used to communicate with the Gunyah Resource Manager.36 Manager VM using Gunyah Message Queues.44 - description: Gunyah capability ID of the TX message queue45 - description: Gunyah capability ID of the RX message queue49 - description: Interrupt for the TX message queue50 - description: Interrupt for the RX message queue
5 Message types24 __u8 type - message type.65 Each connector message can include one or more w1_netlink_msg with87 Replies to W1_LIST_MASTERS should send a message back to the userspace97 Each message is at most 4k in size, so if number of master devices111 [cn_msg, ack = 1 and increasing, 0 means the last message,119 w1_netlink_cmd->len = N * 8; where N is number of IDs in this message.142 as request message except that length parameters do not account for data155 request message (except lengths as described above).162 even if there were errors, only length mismatch interrupts message processing.[all …]
108 the message length, the offset of the message payload, some flags, and a109 transactionID. The portion of the message after the header is114 * Unidirectional: Either side sends a message and does not115 expect a response message116 * Request/response: One side (usually the guest) sends a message126 example, a message sent from the storvsc driver might be "execute127 this SCSI command". If a message also implies some data transfer129 transferred may be embedded with the control message, or it may be136 control message contains a list of GPAs that describe the data144 2. vmbus_sendpacket_pagebuffer(): Message with list of GPAs[all …]