Searched refs:datagram (Results 1 – 25 of 30) sorted by relevance
12
| /linux-6.12.1/Documentation/networking/ |
| D | ipsec.rst | 21 payload, the IP datagram MUST be sent in the original non-compressed
22 form. To clarify: If an IP datagram is sent non-compressed, no
24 IPComp header is added to the datagram. This policy ensures saving
26 datagram fragmentation when the expanded datagram is larger than the
|
| D | phonet.rst | 94 Low-level datagram protocol
97 Applications can send Phonet messages using the Phonet datagram socket
125 A Phonet datagram socket can be subscribed to any number of 8-bits
|
| D | rds.rst | 19 RDS provides reliable, ordered datagram delivery by using a single
374 - copy header to rds_ib_incoming struct if start of a new datagram
376 - if competed datagram:
377 - update cong map if datagram was cong update
384 - find the sock associated with this datagram
|
| D | tipc.rst | 53 Using a service address, a client can send datagram messages to a server socket.
62 datagram mode and in communication group mode.
|
| D | kapi.rst | 32 .. kernel-doc:: net/core/datagram.c
|
| D | checksum-offloads.rst | 85 encapsulated datagram when the inner checksum is due to be offloaded.
130 RCO is a technique for eliding the inner checksum of an encapsulated datagram,
|
| D | segmentation-offloads.rst | 56 datagram into multiple IPv4 fragments. Many of the requirements for UDP
58 fragments should not increment as a single IPv4 datagram is fragmented.
|
| D | dccp.rst | 193 the next pending datagram in bytes, or 0 when no datagram is pending.
|
| D | udplite.rst | 43 UDP-Lite provides a connectionless, unreliable datagram service and hence
|
| D | kcm.rst | 10 datagram sockets.
|
| D | iso15765-2.rst | 79 ``SOCK_DGRAM`` type (as the underlying protocol is datagram-based by design)
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-class-net-cdc_ncm | 48 least one max sized datagram plus headers.
64 least one max sized datagram plus headers.
117 Remainder used to align input datagram payload within
148 Remainder used to align output datagram payload
|
| /linux-6.12.1/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 88 once in a datagram. All multi-octet fields in the option are defined to be
255 for the datagram, and bit N is binary 0 if category N is not part of the
433 datagram. A CIPSO gateway provides IP routing services between two or more
441 datagram for reasons that the information contained can not be adequately
547 addition, the host MUST reject any incoming datagram that has a label which
568 associated with them, either contained in the datagram or assigned to the
572 datagram. See section 4.1.2 for handling procedures for unlabeled
577 recognized the IP datagram is discarded and an ICMP "parameter problem"
583 outside of the configured host or port label range, the datagram is
629 If a CIPSO option is required and none is found, the datagram is
[all …]
|
| /linux-6.12.1/net/phonet/ |
| D | Makefile | 8 datagram.o \
|
| /linux-6.12.1/Documentation/infiniband/ |
| D | ipoib.rst | 36 The IPoIB driver supports two modes of operation: datagram and
40 In datagram mode, the IB UD (Unreliable Datagram) transport is used
68 Stateless offloads are supported only in datagram mode.
|
| /linux-6.12.1/net/caif/ |
| D | cfctrl.c | 90 return p1->u.datagram.connid == p2->u.datagram.connid; in param_eq()
242 tmp32 = cpu_to_le32(param->u.datagram.connid); in cfctrl_linkup_request()
424 linkparam.u.datagram.connid = in cfctrl_recv()
|
| D | cfcnfg.c | 260 l->u.datagram.connid = s->sockaddr.u.dgm.connection_id; in caif_connect_req_to_link_param()
266 l->u.datagram.connid = s->sockaddr.u.dgm.connection_id; in caif_connect_req_to_link_param()
270 l->u.datagram.connid = s->sockaddr.u.rfm.connection_id; in caif_connect_req_to_link_param()
|
| /linux-6.12.1/include/net/caif/ |
| D | cfctrl.h | 73 } datagram; member
|
| /linux-6.12.1/drivers/net/ethernet/mellanox/mlx5/core/ipoib/ |
| D | ipoib.h | 111 struct mlx5_wqe_datagram_seg datagram; member
|
| /linux-6.12.1/net/core/ |
| D | Makefile | 6 obj-y := sock.o request_sock.o skbuff.o datagram.o stream.o scm.o \
|
| /linux-6.12.1/net/ipv6/ |
| D | Makefile | 12 exthdrs.o datagram.o ip6_flowlabel.o inet6_connection_sock.o \
|
| /linux-6.12.1/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | en_tx.c | 984 struct mlx5_wqe_datagram_seg *datagram; in mlx5i_sq_xmit() local
1005 datagram = &wqe->datagram; in mlx5i_sq_xmit()
1009 mlx5i_txwqe_build_datagram(av, dqpn, dqkey, datagram); in mlx5i_sq_xmit()
|
| /linux-6.12.1/net/ipv4/ |
| D | Makefile | 13 tcp_offload.o tcp_plb.o datagram.o raw.o udp.o udplite.o \
|
| /linux-6.12.1/Documentation/filesystems/nfs/ |
| D | rpc-cache.rst | 151 The 'channel' works a bit like a datagram socket. Each 'write' is
|
| /linux-6.12.1/Documentation/userspace-api/ |
| D | landlock.rst | 335 A connected datagram socket behaves like a stream socket when its domain is
338 scenario, a non-connected datagram socket cannot send data (with
|
12