| /linux/Documentation/infiniband/ |
| A D | tag_matching.rst | 14 The ordering rules require that when more than one pair of send and receive
16 and the earliest posted-receive is the pair that must be used to satisfy the
23 corresponding matching receive is posted. If a matching receive is posted,
45 unexpected message list. The application posts receive buffers through calls
46 to the MPI receive routines in the posted receive list and posts send messages
47 using the MPI send routines. The head of the posted receive list may be
50 When send is initiated and arrives at the receive side, if there is no
54 specified receive buffer. This allows overlapping receive-side MPI tag
58 the software unexpected message list for a matching receive. If a match is
63 pre-posted receive to this list, this receive is passed to the hardware.
[all …]
|
| /linux/drivers/staging/greybus/ |
| A D | log.c | 22 struct gb_log_send_log_request *receive; in gb_log_request_handler() local
31 if (op->request->payload_size < sizeof(*receive)) { in gb_log_request_handler()
33 op->request->payload_size, sizeof(*receive)); in gb_log_request_handler()
36 receive = op->request->payload; in gb_log_request_handler()
37 len = le16_to_cpu(receive->len); in gb_log_request_handler()
38 if (len != (op->request->payload_size - sizeof(*receive))) { in gb_log_request_handler()
40 (op->request->payload_size - sizeof(*receive))); in gb_log_request_handler()
54 receive->msg[len - 1] = '\0'; in gb_log_request_handler()
60 dev_dbg(dev, "%s", receive->msg); in gb_log_request_handler()
|
| A D | raw.c | 94 struct gb_raw_send_request *receive; in gb_raw_request_handler() local
103 if (op->request->payload_size < sizeof(*receive)) { in gb_raw_request_handler()
105 op->request->payload_size, sizeof(*receive)); in gb_raw_request_handler()
108 receive = op->request->payload; in gb_raw_request_handler()
109 len = le32_to_cpu(receive->len); in gb_raw_request_handler()
120 return receive_data(raw, len, receive->data); in gb_raw_request_handler()
|
| /linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| A D | mpic-msgr.txt | 25 - mpic-msgr-receive-mask: Specifies what registers in the containing block
26 are allowed to receive interrupts. The value is a bit mask where a set
27 bit at bit 'n' indicates that message register 'n' can receive interrupts.
50 // Message registers 0 and 2 in this block can receive interrupts on
53 mpic-msgr-receive-mask = <0x5>;
59 // Message registers 0 and 2 in this block can receive interrupts on
62 mpic-msgr-receive-mask = <0x5>;
|
| /linux/Documentation/networking/ |
| A D | strparser.rst | 17 The strparser works in one of two modes: receive callback or general
20 In receive callback mode, the strparser is called from the data_ready
33 functions, and a data_ready function for receive callback mode. The
48 socket associated with the stream parser for use with receive
101 maximum messages size is the limit of the receive socket
156 processing a timeout). In receive callback mode the default
165 by the lock callback. In receive callback mode the default
190 the TCP socket in receive callback mode. The stream parser may
220 A timer is set when assembly starts for a new message. In receive
225 socket if in receive callback mode.
[all …]
|
| A D | scaling.rst | 27 Contemporary NICs support multiple receive and transmit descriptor queues
42 stores a queue number. The receive queue for a packet is determined
49 can be directed to their own receive queue. Such “n-tuple” filters can
92 RSS should be enabled when latency is a concern or whenever receive
98 receive queue overflows due to a saturated CPU, because in default
140 Each receive hardware queue has an associated list of CPUs to which
157 can be configured for each receive queue using a sysfs file entry::
384 configured for each receive queue by the driver, so no additional
416 2. XPS using receive queues map
418 This mapping is used to pick transmit queue based on the receive
[all …]
|
| A D | kcm.rst | 9 can efficiently send and receive application protocol messages over TCP using
47 Similarly, in the receive path, messages are constructed on each TCP socket
55 messages on receive as well as other connection specific information for KCM.
63 can be used to send and receive messages from the KCM socket.
98 KCM limits the maximum receive message size to be the size of the receive
189 Disabling receive on KCM socket
193 When receive is disabled, any pending messages in the socket's
194 receive buffer are moved to other sockets. This feature is useful
264 On receive, the KCM module attempts to queue messages received on the
266 changes at each receive ready callback on the KCM socket. The application
[all …]
|
| A D | mctp.rst | 11 The core code provides a socket-based interface to send and receive MCTP
83 Sockets that receive incoming request packets will bind to a local address,
100 The reference to 'incoming' is important here; a bound socket will only receive
111 receive incoming packets from any locally-connected network. A specific network
112 value will cause the socket to only receive incoming messages from that network.
115 ``MCTP_ADDR_ANY`` configures the socket to receive messages addressed to any
118 The ``smctp_type`` field specifies which message types to receive. Only the
169 implicit local socket address, to allow the socket to receive responses to this
173 Sockets will only receive responses to requests they have sent (with TO=1) and
176 ``recvfrom()``, ``recvmsg()``, ``recv()`` : receive an MCTP message
[all …]
|
| /linux/drivers/input/serio/ |
| A D | libps2.c | 230 unsigned int receive = (command >> 8) & 0xf; in __ps2_command() local
235 if (receive > sizeof(ps2dev->cmdbuf)) { in __ps2_command()
250 ps2dev->cmdcnt = receive; in __ps2_command()
251 if (receive && param) in __ps2_command()
252 for (i = 0; i < receive; i++) in __ps2_command()
253 ps2dev->cmdbuf[(receive - 1) - i] = param[i]; in __ps2_command()
298 for (i = 0; i < receive; i++) in __ps2_command()
299 param[i] = ps2dev->cmdbuf[(receive - 1) - i]; in __ps2_command()
317 receive, param ?: send_param); in __ps2_command()
|
| /linux/Documentation/userspace-api/media/rc/ |
| A D | lirc-get-rec-mode.rst | 14 LIRC_GET_REC_MODE/LIRC_SET_REC_MODE - Get/set current receive mode.
34 Mode used for receive.
39 Get and set the current receive mode. Only
|
| A D | lirc-set-rec-carrier.rst | 13 LIRC_SET_REC_CARRIER - Set carrier used to modulate IR receive.
34 Set receive carrier used to modulate IR PWM pulses and spaces.
|
| A D | lirc-set-rec-timeout-reports.rst | 13 LIRC_SET_REC_TIMEOUT_REPORTS - enable or disable timeout reports for IR receive
37 Enable or disable timeout reports for IR receive. By default, timeout reports
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| A D | cirrus,clps711x-intc.txt | 25 13: URXINT1 UART1 receive FIFO half full
29 17: SS2RX SSI2 receive FIFO half or greater full
32 29: URXINT2 UART2 receive FIFO half full
|
| /linux/Documentation/devicetree/bindings/net/can/ |
| A D | renesas,rcar-canfd.yaml | 106 - description: CAN receive FIFO interrupt
109 - description: CAN0 transmit/receive FIFO receive completion interrupt
112 - description: CAN1 transmit/receive FIFO receive completion interrupt
|
| /linux/Documentation/devicetree/bindings/sound/ |
| A D | adi,axi-i2s.txt | 3 The core can be generated with transmit (playback), only receive
15 the core. The core expects two dma channels if both transmit and receive are
17 - dma-names : "tx" for the transmit channel, "rx" for the receive channel.
|
| /linux/net/caif/ |
| A D | cfdgml.c | 34 dgm->layer.receive = cfdgml_receive; in cfdgml_create()
46 caif_assert(layr->receive != NULL); in cfdgml_receive()
61 ret = layr->up->receive(layr->up, pkt); in cfdgml_receive()
|
| A D | cfveil.c | 33 vei->layer.receive = cfvei_receive; in cfvei_create()
44 caif_assert(layr->receive != NULL); in cfvei_receive()
55 ret = layr->up->receive(layr->up, pkt); in cfvei_receive()
|
| A D | cfutill.c | 34 util->layer.receive = cfutill_receive; in cfutill_create()
46 caif_assert(layr->up->receive != NULL); in cfutill_receive()
56 return layr->up->receive(layr->up, pkt); in cfutill_receive()
|
| A D | cfdbgl.c | 27 dbg->layer.receive = cfdbgl_receive; in cfdbgl_create()
35 return layr->up->receive(layr->up, pkt); in cfdbgl_receive()
|
| A D | cfvidl.c | 30 vid->layer.receive = cfvidl_receive; in cfvidl_create()
44 return layr->up->receive(layr->up, pkt); in cfvidl_receive()
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| A D | ixgb.rst | 95 receive.
119 This value is the number of receive descriptors allocated by the driver.
121 Each descriptor is 16 bytes. A receive buffer is also allocated for
124 receive buffer size is 2048 bytes. When the MTU is greater than 1500 the
125 receive buffer size will be either 4056, 8192, or 16384 bytes. The
142 This value delays the generation of receive interrupts in units of
148 run out of available receive descriptors.
205 of Linux to transmit and receive data. The following enhancements were
271 # set maximum receive socket buffer size, default 131071
275 # set default receive socket buffer size, default 65535
[all …]
|
| /linux/Documentation/networking/device_drivers/ethernet/altera/ |
| A D | altera_tse.rst | 42 The SGDMA supports only a single transmit or receive operation at a time, and
91 The driver will post receive buffers to the receive DMA logic during driver
93 underlying DMA logic (MSGDMA is able queue receive buffers, SGDMA is not able
94 to queue receive buffers to the SGDMA receive logic). When a packet is
95 received, the DMA logic generates an interrupt. The driver handles a receive
96 interrupt by obtaining the DMA receive logic status, reaping receive
97 completions until no more receive completions are available.
102 using NAPI for receive operations. Interrupt mitigation is not yet supported
|
| /linux/Documentation/networking/caif/ |
| A D | linux_caif.rst | 82 CAIF payload with receive and transmit functions.
86 to the called function (except for framing layers' receive function)
169 layer->up->receive(layer->up, packet);
182 Net device and Socket implement the 'receive()' function defined by
184 receive of packets is handled as by the rest of the layers: the 'dn->transmit()'
|
| /linux/Documentation/networking/device_drivers/ethernet/neterion/ |
| A D | s2io.rst | 59 and receive, TSO.
61 c. Multi-buffer receive mode. Scattering of packet across multiple
73 f. Multi-FIFO/Ring. Supports up to 8 transmit queues and receive rings,
87 Number of receive rings
101 Size of each receive ring(in 4K blocks)
|
| A D | vxge.rst | 54 - Checksum offload (TCP/UDP/IP) on transmit and receive paths
56 - Generic Receive Offload (GRO) on receive path
78 Up to 17 hardware based transmit and receive data channels, with
|