| /linux-6.12.1/Documentation/infiniband/ |
| 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,
44 There are two types of matching objects used, the posted receive list and the
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
51 pre-posted receive for this arriving message, it is passed to the software and
54 specified receive buffer. This allows overlapping receive-side MPI tag
[all …]
|
| /linux-6.12.1/drivers/staging/greybus/ |
| 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()
|
| D | raw.c | 97 struct gb_raw_send_request *receive; in gb_raw_request_handler() local
106 if (op->request->payload_size < sizeof(*receive)) { in gb_raw_request_handler()
108 op->request->payload_size, sizeof(*receive)); in gb_raw_request_handler()
111 receive = op->request->payload; in gb_raw_request_handler()
112 len = le32_to_cpu(receive->len); in gb_raw_request_handler()
123 return receive_data(raw, len, receive->data); in gb_raw_request_handler()
|
| /linux-6.12.1/Documentation/devicetree/bindings/powerpc/fsl/ |
| 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-6.12.1/Documentation/networking/device_drivers/can/freescale/ |
| D | flexcan.rst | 19 and i.MX53 SOCs) only receive RTR frames if the controller is
30 With the "rx-rtr" private flag the ability to receive RTR frames can
31 be waived at the expense of losing the ability to receive RTR
37 The CAN controller can and will receive RTR frames.
39 On some IP cores the controller cannot receive RTR frames in the
45 Waive ability to receive RTR frames. (not supported on all IP cores)
|
| /linux-6.12.1/Documentation/networking/ |
| 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
102 buffer and message timeout is the receive timeout for the socket.
144 zero) and the parser is in receive callback mode, then it will set
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
[all …]
|
| D | oa-tc6-framework.rst | 59 receive (RX) chunks. Chunks in both transmit and receive directions may
69 In parallel, receive data chunks are received on MISO. Each receive data
71 The data footer indicates if there is receive frame data present within
189 any receive frame data within the current chunk.
200 chunk payload. Note that the receive path is unaffected by
254 host will be sent as multiple receive data chunks. Each receive data
257 location of the receive frame data within the 64 bytes data chunk payload.
285 the SPI host the minimum number of additional receive
287 reading beyond the current receive data chunk. This
288 field is zero when there is no receive frame data
[all …]
|
| D | scaling.rst | 27 Contemporary NICs support multiple receive and transmit descriptor queues
31 of logical flows. Packets for each flow are steered to a separate receive
42 stores a queue number. The receive queue for a packet is determined
64 can be directed to their own receive queue. Such “n-tuple” filters can
74 num_queues. A typical RSS configuration would be to have one receive queue
91 Each receive queue has a separate IRQ associated with it. The NIC triggers
97 processing takes place in receive interrupt handling, it is advantageous
98 to spread receive interrupts between CPUs. To manually adjust the IRQ
107 RSS should be enabled when latency is a concern or whenever receive
112 is likely the one with the smallest number of receive queues where no
[all …]
|
| D | tc-queue-filters.rst | 8 to a single queue on both the transmit and receive side.
22 Likewise, on the receive side, the two filters for selecting set of
31 receive queue. The action skbedit queue_mapping for receive queue
|
| 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
105 A timeout may be set for assembling messages on a receive socket. The timeout
106 value is taken from the receive timeout of the attached TCP socket (this is set
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
[all …]
|
| 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-6.12.1/drivers/input/serio/ |
| D | libps2.c | 269 unsigned int receive = (command >> 8) & 0xf; in __ps2_command() local
274 if (receive > sizeof(ps2dev->cmdbuf)) { in __ps2_command()
288 ps2dev->cmdcnt = receive; in __ps2_command()
310 if (receive) { in __ps2_command()
314 for (i = 0; i < receive; i++) in __ps2_command()
315 ps2dev->cmdbuf[(receive - 1) - i] = param[i]; in __ps2_command()
356 for (i = 0; i < receive; i++) in __ps2_command()
357 param[i] = ps2dev->cmdbuf[(receive - 1) - i]; in __ps2_command()
358 kmsan_unpoison_memory(param, receive); in __ps2_command()
377 receive, param ?: send_param); in __ps2_command()
|
| /linux-6.12.1/Documentation/userspace-api/media/rc/ |
| 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
|
| 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.
|
| /linux-6.12.1/Documentation/devicetree/bindings/interrupt-controller/ |
| 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-6.12.1/tools/testing/selftests/net/packetdrill/ |
| D | tcp_zerocopy_epoll_edge.pkt | 7 // fire two sends with MSG_ZEROCOPY and receive the acks. confirm that EPOLLERR
37 // receive only one EPOLLERR for the two sends above.
45 // receive only one EPOLLERR for the third send above.
|
| D | tcp_zerocopy_epoll_exclusive.pkt | 8 // fire two sends with MSG_ZEROCOPY and receive the acks. confirm that EPOLLERR
39 // receive only one EPOLLERR for the two sends above.
47 // receive only one EPOLLERR for the third send above.
|
| D | tcp_zerocopy_epoll_oneshot.pkt | 7 // fire two sends with MSG_ZEROCOPY and receive the acks. confirm that EPOLLERR
38 // receive only one EPOLLERR for the two sends above.
46 // receive no EPOLLERR for the third send above.
|
| /linux-6.12.1/net/caif/ |
| 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()
|
| 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()
|
| 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()
|
| D | cfdbgl.c | 27 dbg->layer.receive = cfdbgl_receive; in cfdbgl_create()
35 return layr->up->receive(layr->up, pkt); in cfdbgl_receive()
|
| D | cfvidl.c | 30 vid->layer.receive = cfvidl_receive; in cfvidl_create()
44 return layr->up->receive(layr->up, pkt); in cfvidl_receive()
|
| /linux-6.12.1/Documentation/devicetree/bindings/sound/ |
| 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-6.12.1/Documentation/networking/device_drivers/ethernet/altera/ |
| 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
|