| /Linux-v4.19/Documentation/infiniband/ |
| D | tag_matching.txt | 10 The ordering rules require that when more than one pair of send and receive
12 and the earliest posted-receive is the pair that must be used to satisfy the
19 corresponding matching receive is posted. If a matching receive is posted,
39 There are two types of matching objects used, the posted receive list and the
40 unexpected message list. The application posts receive buffers through calls
41 to the MPI receive routines in the posted receive list and posts send messages
42 using the MPI send routines. The head of the posted receive list may be
45 When send is initiated and arrives at the receive side, if there is no
46 pre-posted receive for this arriving message, it is passed to the software and
49 specified receive buffer. This allows overlapping receive-side MPI tag
[all …]
|
| /Linux-v4.19/drivers/staging/greybus/ |
| D | log.c | 23 struct gb_log_send_log_request *receive; in gb_log_request_handler() local
32 if (op->request->payload_size < sizeof(*receive)) { in gb_log_request_handler()
34 op->request->payload_size, sizeof(*receive)); in gb_log_request_handler()
37 receive = op->request->payload; in gb_log_request_handler()
38 len = le16_to_cpu(receive->len); in gb_log_request_handler()
39 if (len != (op->request->payload_size - sizeof(*receive))) { in gb_log_request_handler()
41 (op->request->payload_size - sizeof(*receive))); in gb_log_request_handler()
55 receive->msg[len - 1] = '\0'; in gb_log_request_handler()
61 dev_dbg(dev, "%s", receive->msg); in gb_log_request_handler()
|
| D | raw.c | 95 struct gb_raw_send_request *receive; in gb_raw_request_handler() local
104 if (op->request->payload_size < sizeof(*receive)) { in gb_raw_request_handler()
106 op->request->payload_size, sizeof(*receive)); in gb_raw_request_handler()
109 receive = op->request->payload; in gb_raw_request_handler()
110 len = le32_to_cpu(receive->len); in gb_raw_request_handler()
121 return receive_data(raw, len, receive->data); in gb_raw_request_handler()
|
| /Linux-v4.19/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-v4.19/drivers/input/serio/ |
| D | libps2.c | 234 unsigned int receive = (command >> 8) & 0xf; in __ps2_command() local
239 if (receive > sizeof(ps2dev->cmdbuf)) { in __ps2_command()
254 ps2dev->cmdcnt = receive; in __ps2_command()
255 if (receive && param) in __ps2_command()
256 for (i = 0; i < receive; i++) in __ps2_command()
257 ps2dev->cmdbuf[(receive - 1) - i] = param[i]; in __ps2_command()
302 for (i = 0; i < receive; i++) in __ps2_command()
303 param[i] = ps2dev->cmdbuf[(receive - 1) - i]; in __ps2_command()
321 receive, param ?: send_param); in __ps2_command()
|
| /Linux-v4.19/Documentation/networking/ |
| D | strparser.txt | 13 The strparser works in one of two modes: receive callback or general
16 In receive callback mode, the strparser is called from the data_ready
29 functions, and a data_ready function for receive callback mode. The
42 socket associated with the stream parser for use with receive
83 maximum messages size is the limit of the receive socket
84 buffer and message timeout is the receive timeout for the socket.
120 zero) and the parser is in receive callback mode, then it will set
130 processing a timeout). In receive callback mode the default
137 by the lock callback. In receive callback mode the default
158 the TCP socket in receive callback mode. The stream parser may
[all …]
|
| D | scaling.txt | 23 Contemporary NICs support multiple receive and transmit descriptor queues
27 of logical flows. Packets for each flow are steered to a separate receive
38 stores a queue number. The receive queue for a packet is determined
45 can be directed to their own receive queue. Such “n-tuple” filters can
53 num_queues. A typical RSS configuration would be to have one receive queue
68 Each receive queue has a separate IRQ associated with it. The NIC triggers
74 processing takes place in receive interrupt handling, it is advantageous
75 to spread receive interrupts between CPUs. To manually adjust the IRQ
82 RSS should be enabled when latency is a concern or whenever receive
87 is likely the one with the smallest number of receive queues where no
[all …]
|
| D | kcm.txt | 6 can efficiently send and receive application protocol messages over TCP using
44 Similarly, in the receive path, messages are constructed on each TCP socket
52 messages on receive as well as other connection specific information for KCM.
60 can be used to send and receive messages from the KCM socket.
95 KCM limits the maximum receive message size to be the size of the receive
102 A timeout may be set for assembling messages on a receive socket. The timeout
103 value is taken from the receive timeout of the attached TCP socket (this is set
185 Disabling receive on KCM socket
189 When receive is disabled, any pending messages in the socket's
190 receive buffer are moved to other sockets. This feature is useful
[all …]
|
| D | netvsc.txt | 22 Hyper-V supports receive side scaling. For TCP & UDP, packets can
66 Packets are received into a receive area which is created when device
67 is probed. The receive area is broken into MTU sized chunks and each may
68 contain one or more packets. The number of receive sections may be changed
|
| D | s2io.txt | 44 and receive, TSO.
46 c. Multi-buffer receive mode. Scattering of packet across multiple
58 f. Multi-FIFO/Ring. Supports up to 8 transmit queues and receive rings,
68 Number of receive rings
78 Size of each receive ring(in 4K blocks)
|
| D | altera_tse.txt | 36 The SGDMA supports only a single transmit or receive operation at a time, and
74 The driver will post receive buffers to the receive DMA logic during driver
76 underlying DMA logic (MSGDMA is able queue receive buffers, SGDMA is not able
77 to queue receive buffers to the SGDMA receive logic). When a packet is
78 received, the DMA logic generates an interrupt. The driver handles a receive
79 interrupt by obtaining the DMA receive logic status, reaping receive
80 completions until no more receive completions are available.
84 using NAPI for receive operations. Interrupt mitigation is not yet supported
|
| D | vxge.txt | 45 Checksum offload (TCP/UDP/IP) on transmit and receive paths
47 Generic Receive Offload (GRO) on receive path
64 Up to 17 hardware based transmit and receive data channels, with
|
| /Linux-v4.19/Documentation/media/uapi/rc/ |
| D | lirc-get-rec-mode.rst | 13 LIRC_GET_REC_MODE/LIRC_SET_REC_MODE - Get/set current receive mode.
31 Mode used for receive.
36 Get and set the current receive mode. Only
|
| D | lirc-set-rec-timeout-reports.rst | 12 LIRC_SET_REC_TIMEOUT_REPORTS - enable or disable timeout reports for IR receive
36 Enable or disable timeout reports for IR receive. By default, timeout reports
|
| D | lirc-set-rec-carrier.rst | 12 LIRC_SET_REC_CARRIER - Set carrier used to modulate IR receive.
33 Set receive carrier used to modulate IR PWM pulses and spaces.
|
| /Linux-v4.19/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-v4.19/Documentation/isdn/ |
| D | INTERFACE.fax | 18 In receive-mode the LL-driver takes care of the bit-order conversion
67 Defines outgoing/send or incoming/receive connection.
87 (+FCSI/+FTSI on send/receive)
112 ISDN_TTY_FAX_TRAIN_OK output of +FDCS and OK message (for receive mode).
114 ISDN_TTY_FAX_EOP signals end of data in receive mode,
132 Set by HL in receive-mode for +FET message.
|
| /Linux-v4.19/net/caif/ |
| 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 | cfdgml.c | 34 dgm->layer.receive = cfdgml_receive; in cfdgml_create()
47 caif_assert(layr->receive != NULL); in cfdgml_receive()
62 ret = layr->up->receive(layr->up, pkt); in cfdgml_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-v4.19/Documentation/devicetree/bindings/sound/ |
| D | adi,axi-i2s.txt | 13 receive.
14 - dma-names : "tx" for the transmit channel, "rx" for the receive channel.
|
| /Linux-v4.19/Documentation/devicetree/bindings/spi/ |
| D | microchip,spi-pic32.txt | 7 of <fault-irq>, <receive-irq>, <transmit-irq>.
18 named "spi-tx" for transmit and named "spi-rx" for receive.
|
| /Linux-v4.19/Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 69 CAIF payload with receive and transmit functions.
73 to the called function (except for framing layers' receive function)
151 layer->up->receive(layer->up, packet);
162 Net device and Socket implement the 'receive()' function defined by
164 receive of packets is handled as by the rest of the layers: the 'dn->transmit()'
|
