Home
last modified time | relevance | path

Searched refs:datagrams (Results 1 – 25 of 45) sorted by relevance

12

/freebsd/crypto/openssl/doc/man3/
H A DBIO_sendmmsg.pod7 BIO_err_is_non_fatal - send and receive multiple datagrams in a single call
63 When these functions are used to send and receive datagrams, the I<peer> field
64 of a B<BIO_MSG> allows the destination address of sent datagrams to be specified
65 on a per-datagram basis, and the source address of received datagrams to be
68 datagrams, and written by BIO_recvmmsg() with the source address of received
69 datagrams.
72 datagrams to be specified on a per-datagram basis, and the destination address
73 of received datagrams to be determined. Unlike I<peer>, support for I<local>
H A DBIO_s_datagram.pod56 datagrams from the specified peer. Any other socket is an unconnected socket and
57 can receive datagrams from any host.
73 calls BIO_read(), any host on the network may cause future datagrams written to
187 Fragment mode, in which datagrams will be set with the IP Don't Fragment (DF)
208 supported by the applicable underlying network layer. Use of datagrams of this
228 peek mode is enabled, calls to L<BIO_read(3)> read datagrams from the underlying
H A DBIO_s_dgram_pair.pod78 This BIO does not support sending or receiving zero-length datagrams. Passing a
135 The BIO datagram pair can be used to enqueue datagrams which have source and
139 example, if datagrams are queued with destination addresses set but simply read
160 with datagrams written to the BIO pair.
165 with datagrams written to the BIO pair.
197 provide source and destination addresses respectively when writing datagrams to
H A DBIO_s_mem.pod40 wrote more datagrams. Each successive call to L<BIO_read(3)> will read the next
46 this case will return 0 and no datagrams will be written. Calling L<BIO_read(3)>
47 when there are no datagrams in the BIO to read will return a negative result and
H A DSSL_inject_net_dgram.pod20 This function can be used for debugging purposes or to allow datagrams to be fed
/freebsd/tests/sys/netinet6/frag6/
H A Dfrag6_05.sh73 <received-datagrams>0</received-datagrams>
266 <received-datagrams>0</received-datagrams>
H A Dfrag6_07.sh64 <received-datagrams>0</received-datagrams>
H A Dfrag6_03.sh69 <received-datagrams>2</received-datagrams>
H A Dfrag6_08.sh64 <received-datagrams>0</received-datagrams>
H A Dfrag6_09.sh69 <received-datagrams>0</received-datagrams>
H A Dfrag6_20.sh64 <received-datagrams>0</received-datagrams>
H A Dfrag6_02.sh69 <received-datagrams>0</received-datagrams>
H A Dfrag6_04.sh69 <received-datagrams>0</received-datagrams>
H A Dfrag6_10.sh69 <received-datagrams>0</received-datagrams>
H A Dfrag6_11.sh69 <received-datagrams>0</received-datagrams>
H A Dfrag6_12.sh69 <received-datagrams>0</received-datagrams>
H A Dfrag6_13.sh69 <received-datagrams>0</received-datagrams>
H A Dfrag6_14.sh69 <received-datagrams>0</received-datagrams>
H A Dfrag6_16.sh65 <received-datagrams>1</received-datagrams>
H A Dfrag6_19.sh53 <received-datagrams>0</received-datagrams>
H A Dfrag6_15.sh87 <received-datagrams>0</received-datagrams>
H A Dfrag6_06.sh87 <received-datagrams>0</received-datagrams>
/freebsd/crypto/openssl/doc/designs/quic-design/
H A Ddgram-api.md5 eventual BIO_dgram_mem) to support APIs which allow multiple datagrams to be
301 datagrams, thereby still avoiding extra syscalls but offering a simple API.
323 iovecs for its `readmmsg` call, and the received datagrams can then be popped by
387 and agglomerate multiple datagrams into a single BIO call. Unless we only
389 datagrams from the same function immediately after one another... doesn't
412 a. Use `recvmmsg` and add the received datagrams to an RX queue just as for the
414 (`OPENSSL_malloc`) and flag these datagrams as needing to be freed by OpenSSL,
437 For (3) we have a legacy `BIO_read` but we have several datagrams still in the
486 If BIO_dgram is freed before all datagrams are read, the read buffer free
H A Dquic-fault-injector.md6 a misbehaving peer, i.e. one which is sending protocol elements (e.g. datagrams,
135 Encrypted QUIC packets are sent in datagrams. There may be more than one QUIC
137 faults directly into these datagrams.
150 datagrams sent from the client on to the server, and vice versa. Where a test
370 * Enable tests to listen for datagrams being sent
/freebsd/sys/compat/linux/
H A Dlinux_socket.c1599 int error, datagrams; in linux_sendmmsg() local
1605 datagrams = 0; in linux_sendmmsg()
1606 while (datagrams < args->vlen) { in linux_sendmmsg()
1617 ++datagrams; in linux_sendmmsg()
1620 td->td_retval[0] = datagrams; in linux_sendmmsg()
2018 int error, datagrams; in linux_recvmmsg_common() local
2023 datagrams = 0; in linux_recvmmsg_common()
2024 while (datagrams < vlen) { in linux_recvmmsg_common()
2035 ++datagrams; in linux_recvmmsg_common()
2057 td->td_retval[0] = datagrams; in linux_recvmmsg_common()

12