Lines Matching full:structures

19 - We define our own structures rather than using the OS's `struct mmsghdr`.
25   - It allows us to use structures in keeping with OpenSSL's existing
80     structures (as discussed above) and also intend these functions to be
81     stateless and not requiire locking. Therefore the OS-native iovec structures
123 - `msg` points to an array of `num_msg` `BIO_MSG` structures.
147 - `peer` and `local` are optional pointers to `BIO_ADDR` structures into
188 structures through to the syscall without copying them.
203   for OS-provided structures, or our own independent structure
206   - If we use OS-provided structures:
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:
217     - We would need to translate these structures during every call.
230       will need a fixed stack allocation of OS iovec structures and we can
365 argument structures, requiring constant revision of the central read/write