Lines Matching full:our
19 - We define our own structures rather than using the OS's `struct mmsghdr`.
31 - It avoids the need to include OS headers in our own public headers,
33 our headers, potentially undesirably.
44 - We ensure the extensibility of our `BIO_MSG` structure in a way that preserves
67 defeat all of the advantages of iovecs and prevent us from meeting our
71 - We do not believe iovecs are needed to meet our performance requirements
79 on the number of iovecs supported, because we translate from our own
203 for OS-provided structures, or our own independent structure
209 structures in our public API headers.
212 (see discussion below), We would need to define our own structures in this
215 - If we use our own structures:
233 until we reach our iovec limit, and then return.
385 We probably want this for our own QUIC implementation built on top of this
397 applications. *But* the primary consumer of this new API will be our own
475 mention this only for completeness. Our recent learnt lessons on cache