Previous  Up  Next

Module Iobuf

module Iobuf: sig .. end
A non-moving (in the GC sense) contiguous range of bytes, useful for I/O operations.

An iobuf consists of:

All iobuf operations are restricted to operate within the limits. Initially, the window of an iobuf is identical to the limits. A phantom type, "seek" permission, controls whether or not code is allowed to change the limits and window. With seek permission, the limits can be narrowed, but can never be widened, and the window can be set to an arbitrary subrange of the limits.

A phantom type controls whether code can read and write bytes in the bigstring (within the limits) or can only read them.

To present a restricted view of an iobuf to a client, one can create a sub-iobuf or add a type constraint.

include ??
include ??
type (-'data_perm_read_write, +'seek_permission) t
The first type parameter controls whether the iobuf can be written to. The second type parameter controls whether the window and limits can be changed.

See the Perms module for information on how the first type parameter is used.

To allow no_seek or seek access, a function's type uses _ rather than no_seek as the type argument to t. Using _ allows the function to be directly applied to either permission. Using a specific permission would require code to use coercion :>.

include Invariant.S2

Creation


val create : len:int -> ('a, 'b) t
create ~len creates a new iobuf, backed by a bigstring of length len, with the limits and window set to the entire bigstring.
val of_bigstring : ?pos:int ->
       ?len:int ->
       Core_kernel.Std.Bigstring.t -> ([< Core_kernel.Std.read_write ], 'a) t
of_bigstring bigstring ~pos ~len returns an iobuf backed by bigstring, with the window and limits specified starting at pos and of length len.

forbid immutable to prevent aliasing

val of_string : string -> ('a, 'b) t
of_string s returns a new iobuf whose contents are s.
val sub_shared : ?pos:int -> ?len:int -> ('d, 'a) t -> ('d, 'b) t
sub_shared t ~pos ~len returns a new iobuf with limits and window set to the subrange of t specified by pos and len. sub_shared preserves data permissions, but allows arbitrary seek permissions on the resulting iobuf.
val set_bounds_and_buffer : src:([> Core_kernel.Std.write ] as 'data, 'a) t ->
       dst:('data, seek) t -> unit
set_bounds_and_buffer ~src ~dst copies bounds metadata (i.e., limits and window) and shallowly copies the buffer (data pointer) from src to dst. It does not access data, but does allow access through dst. This makes dst an alias of src.

Because set_bounds_and_buffer creates an alias, we disallow immutable src and dst using [> write]. Otherwise, one of src or dst could be read_write :> read and the other immutable :> read, which would allow to write the immutable alias's data through the read_write alias.

set_bounds_and_buffer is typically used to allocate a frame iobuf only once. This frame can be updated repeatedly and handed to users, without further allocation. Only the most allocation-sensitive applications need this.

val set_bounds_and_buffer_sub : ?pos:int ->
       ?len:int ->
       src:([> Core_kernel.Std.write ] as 'data, 'a) t ->
       dst:('data, seek) t -> unit -> unit
set_bounds_and_buffer_sub ?pos ?len ~src ~dst () is a more efficient version of: set_bounds_and_buffer ~src:(Iobuf.sub_shared ?pos ?len src) ~dst.

set_bounds_and_buffer ~src ~dst is not the same as set_bounds_and_buffer_sub ~dst ~src () because the limits are narrowed in the latter case.

val read_only : ([> Core_kernel.Std.read ], 's) t -> (Core_kernel.Std.read, 's) t

Generalization

One may wonder why you'd want to call no_seek, given that a cast is already possible, e.g. t : (_, seek) t :> (_, no_seek) t. It turns out that if you want to define some f : (_, _) t -> unit of your own, which can be conveniently applied to seek iobufs without the user having to cast seek up, you need this no_seek function.

read_only is more of an historical convenience now that read_write is a polymorphic variant, as one can now explicitly specify the general type for an argument with something like t : (_ perms, _) t :> (read, _) t.

val no_seek : ('r, 'a) t -> ('r, no_seek) t

Accessors


val capacity : ('a, 'b) t -> int
capacity t returns the size of t's limits subrange. The capacity of an iobuf can be reduced via narrow.
val length : ('a, 'b) t -> int
length t returns the size of t's window.
val is_empty : ('a, 'b) t -> bool
is_empty t is length t = 0.

Changing the limits


val narrow : ('a, seek) t -> unit
narrow t sets t's limits to the current window.
val narrow_lo : ('a, seek) t -> unit
narrow_lo t sets t's lower limit to the beginning of the current window.
val narrow_hi : ('a, seek) t -> unit
narrow_hi t sets t's upper limit to the end of the current window.

Changing the window



One can call Lo_bound.window t to get a snapshot of the lower bound of the window, and then later restore that snapshot with Lo_bound.restore. This is useful for speculatively parsing, and then rewinding when there isn't enough data to finish.

Similarly for Hi_bound.window and Lo_bound.restore.

Using a snapshot with a different iobuf, even a sub iobuf of the snapshotted one, has unspecified results. An exception may be raised, or a silent error may occur. However, the safety guarantees of the iobuf will not be violated, i.e., the attempt will not enlarge the limits of the subject iobuf.

module type Bound = Bound  with type ('d, 'w) iobuf := ('d, 'w) t
module Lo_bound: Bound 
module Hi_bound: Bound 
val advance : ('a, seek) t -> int -> unit
advance t amount advances the lower bound of the window by amount. It is an error to advance past the upper bound of the window or the lower limit.
val unsafe_advance : ('a, seek) t -> int -> unit
unsafe_advance is like advance but with no bounds checking, so incorrect usage can easily cause segfaults.
val resize : ('a, seek) t -> len:int -> unit
resize t sets the length of t's window, provided it does not exceed limits.
val unsafe_resize : ('a, seek) t -> len:int -> unit
unsafe_resize is like resize but with no bounds checking, so incorrect usage can easily cause segfaults.
val rewind : ('a, seek) t -> unit
rewind t sets the lower bound of the window to the lower limit.
val reset : ('a, seek) t -> unit
reset t sets the window to the limits.
val flip_lo : ('a, seek) t -> unit
flip_lo t sets the window to range from the lower limit to the lower bound of the old window. This is typically called after a series of Fills, to reposition the window in preparation to Consume the newly written data.

The bounded version narrows the effective limit. This can preserve some data near the limit, such as an hypothetical packet header, in the case of bounded_flip_lo or unfilled suffix of a buffer, in bounded_flip_hi.

val bounded_flip_lo : ('a, seek) t -> Lo_bound.t -> unit
val compact : (Core_kernel.Std.read_write, seek) t -> unit
compact t copies data from the window to the lower limit of the iobuf and sets the window to range from the end of the copied data to the upper limit. This is typically called after a series of Consumes to save unread data and prepare for the next series of Fills and flip_lo.
val bounded_compact : (Core_kernel.Std.read_write, seek) t ->
       Lo_bound.t -> Hi_bound.t -> unit
val flip_hi : ('a, seek) t -> unit
flip_hi t sets the window to range from the the upper bound of the current window to the upper limit. This operation is dual to flip_lo and is typically called when the data in the current (narrowed) window has been processed and the window needs to be positioned over the remaining data in the buffer. For example: 

      (* ... determine initial_data_len ... *)
      Iobuf.resize buf ~len:initial_data_len;
      (* ... and process initial data ... *)
      Iobuf.flip_hi buf;

Now the window of buf ranges over the remainder of the data.

val bounded_flip_hi : ('a, seek) t -> Hi_bound.t -> unit
val protect_window_and_bounds : ('rw, no_seek) t -> f:(('rw, seek) t -> 'a) -> 'a
protect_window_and_bounds t ~f applies f to t and restores t's bounds afterwards.

Getting and setting data



"consume" and "fill" functions access data at the lower bound of the window and advance lower bound of the window. "peek" and "poke" functions access data but do not advance the window.
val to_string : ?len:int -> ([> Core_kernel.Std.read ], 'a) t -> string
to_string t returns the bytes in t as a string. It does not alter the window.
val to_string_hum : ?bounds:[ `Limits | `Whole | `Window ] ->
       ([> Core_kernel.Std.read ], 'a) t -> string
to_string_hum t produces a readable, multi-line representation of an iobuf. bounds defaults to `Limits and determines how much of the contents are shown.
module Consume: sig .. end
Consume.string t ~len reads len characters (all, by default) from t into a new string and advances the lower bound of the window accordingly. 
module Fill: sig .. end
Fill.bin_prot X.bin_write_t t x writes x to t in bin-prot form, advancing past the bytes written. 
module Peek: sig .. end
Peek and Poke functions access a value at pos from the lower bound of the window and do not advance. 
module Poke: sig .. end
Poke.bin_prot X.bin_write_t t x writes x to the beginning of t in binary form without advancing. 
module Unsafe: sig .. end
Unsafe has submodules that are like their corresponding module, except with no range checks. 
val crc32 : ([> Core_kernel.Std.read ], 'a) t -> Core_kernel.Std.Int63.t
val fill_bin_prot : (Core_kernel.Std.read_write, seek) t ->
       'a Core_kernel.Std.Bin_prot.Type_class.writer ->
       'a -> unit Core_kernel.Std.Or_error.t
fill_bin_prot writes a bin-prot value to the lower bound of the window, prefixed by its length, and advances by the amount written. fill_bin_prot returns an error if the window is too small to write the value.

consume_bin_prot t reader reads a bin-prot value from the lower bound of the window, which should have been written using fill_bin_prot, and advances the window by the amount read. consume_bin_prot returns an error if there is not a complete message in the window and in that case the window is left unchanged.

Don't use these without a good reason, as they are incompatible with similar functions in Reader and Writer. They use a 4-byte length rather than an 8-byte length.

val consume_bin_prot : ([> Core_kernel.Std.read ], seek) t ->
       'a Core_kernel.Std.Bin_prot.Type_class.reader ->
       'a Core_kernel.Std.Or_error.t
module Blit: sig .. end
Blit copies between iobufs and advances neither src nor dst. 
module Blit_consume: sig .. end
Blit_consume copies between iobufs and advances src but does not advance dst. 
module Blit_fill: sig .. end
Blit_fill copies between iobufs and advances dst but does not advance src. 
module Blit_consume_and_fill: sig .. end
Blit_consume_and_fill copies between iobufs and advances both src and dst.

I/O


val read_assume_fd_is_nonblocking : (Core_kernel.Std.read_write, seek) t ->
       Iobuf_intf.Unix.File_descr.t -> Syscall_result.Unit.t
Iobuf has analogs of various Bigstring functions. These analogs advance by the amount written/read.
val pread_assume_fd_is_nonblocking : (Core_kernel.Std.read_write, seek) t ->
       Iobuf_intf.Unix.File_descr.t -> offset:int -> unit
val recvfrom_assume_fd_is_nonblocking : (Core_kernel.Std.read_write, seek) t ->
       Iobuf_intf.Unix.File_descr.t -> Iobuf_intf.Unix.sockaddr
val recvmmsg_assume_fd_is_nonblocking : (Iobuf_intf.Unix.File_descr.t ->
        ?count:int ->
        ?srcs:Iobuf_intf.Unix.sockaddr array ->
        (Core_kernel.Std.read_write, seek) t array ->
        Iobuf_intf.Unix.Syscall_result.Int.t)
       Core_kernel.Std.Or_error.t
val recvmmsg_assume_fd_is_nonblocking_no_options : (Iobuf_intf.Unix.File_descr.t ->
        count:int ->
        (Core_kernel.Std.read_write, seek) t array ->
        Iobuf_intf.Unix.Syscall_result.Int.t)
       Core_kernel.Std.Or_error.t
val send_nonblocking_no_sigpipe : unit ->
       (([> Core_kernel.Std.read ], seek) t ->
        Iobuf_intf.Unix.File_descr.t -> Iobuf_intf.Unix.Syscall_result.Unit.t)
       Core_kernel.Std.Or_error.t
val sendto_nonblocking_no_sigpipe : unit ->
       (([> Core_kernel.Std.read ], seek) t ->
        Iobuf_intf.Unix.File_descr.t ->
        Iobuf_intf.Unix.sockaddr -> Iobuf_intf.Unix.Syscall_result.Unit.t)
       Core_kernel.Std.Or_error.t
val write_assume_fd_is_nonblocking : ([> Core_kernel.Std.read ], seek) t ->
       Iobuf_intf.Unix.File_descr.t -> unit
val pwrite_assume_fd_is_nonblocking : ([> Core_kernel.Std.read ], seek) t ->
       Iobuf_intf.Unix.File_descr.t -> offset:int -> unit

Expert


module Expert: sig .. end
The Expert module is for building efficient out-of-module Iobuf abstractions. 
val sexp_of_seek : seek -> Sexplib.Sexp.t
val sexp_of_no_seek : no_seek -> Sexplib.Sexp.t
val sexp_of_t : ('data_perm_read_write -> Sexplib.Sexp.t) ->
       ('seek_permission -> Sexplib.Sexp.t) ->
       ('data_perm_read_write, 'seek_permission) t -> Sexplib.Sexp.t
The first type parameter controls whether the iobuf can be written to. The second type parameter controls whether the window and limits can be changed.

See the Perms module for information on how the first type parameter is used.

To allow no_seek or seek access, a function's type uses _ rather than no_seek as the type argument to t. Using _ allows the function to be directly applied to either permission. Using a specific permission would require code to use coercion :>.


Creation



create ~len creates a new iobuf, backed by a bigstring of length len, with the limits and window set to the entire bigstring.

of_bigstring bigstring ~pos ~len returns an iobuf backed by bigstring, with the window and limits specified starting at pos and of length len.

default is 0

default is Bigstring.length bigstring - pos

forbid immutable to prevent aliasing

of_string s returns a new iobuf whose contents are s.

sub_shared t ~pos ~len returns a new iobuf with limits and window set to the subrange of t specified by pos and len. sub_shared preserves data permissions, but allows arbitrary seek permissions on the resulting iobuf.

set_bounds_and_buffer ~src ~dst copies bounds metadata (i.e., limits and window) and shallowly copies the buffer (data pointer) from src to dst. It does not access data, but does allow access through dst. This makes dst an alias of src.

Because set_bounds_and_buffer creates an alias, we disallow immutable src and dst using [> write]. Otherwise, one of src or dst could be read_write :> read and the other immutable :> read, which would allow to write the immutable alias's data through the read_write alias.

set_bounds_and_buffer is typically used to allocate a frame iobuf only once. This frame can be updated repeatedly and handed to users, without further allocation. Only the most allocation-sensitive applications need this.

set_bounds_and_buffer_sub ?pos ?len ~src ~dst () is a more efficient version of: set_bounds_and_buffer ~src:(Iobuf.sub_shared ?pos ?len src) ~dst.

set_bounds_and_buffer ~src ~dst is not the same as set_bounds_and_buffer_sub ~dst ~src () because the limits are narrowed in the latter case.

Generalization

One may wonder why you'd want to call no_seek, given that a cast is already possible, e.g. t : (_, seek) t :> (_, no_seek) t. It turns out that if you want to define some f : (_, _) t -> unit of your own, which can be conveniently applied to seek iobufs without the user having to cast seek up, you need this no_seek function.

read_only is more of an historical convenience now that read_write is a polymorphic variant, as one can now explicitly specify the general type for an argument with something like t : (_ perms, _) t :> (read, _) t.

Accessors



capacity t returns the size of t's limits subrange. The capacity of an iobuf can be reduced via narrow.

length t returns the size of t's window.

is_empty t is length t = 0.

Changing the limits



narrow t sets t's limits to the current window.

narrow_lo t sets t's lower limit to the beginning of the current window.

narrow_hi t sets t's upper limit to the end of the current window.

Changing the window



One can call Lo_bound.window t to get a snapshot of the lower bound of the window, and then later restore that snapshot with Lo_bound.restore. This is useful for speculatively parsing, and then rewinding when there isn't enough data to finish.

Similarly for Hi_bound.window and Lo_bound.restore.

Using a snapshot with a different iobuf, even a sub iobuf of the snapshotted one, has unspecified results. An exception may be raised, or a silent error may occur. However, the safety guarantees of the iobuf will not be violated, i.e., the attempt will not enlarge the limits of the subject iobuf.

advance t amount advances the lower bound of the window by amount. It is an error to advance past the upper bound of the window or the lower limit.

unsafe_advance is like advance but with no bounds checking, so incorrect usage can easily cause segfaults.

resize t sets the length of t's window, provided it does not exceed limits.

unsafe_resize is like resize but with no bounds checking, so incorrect usage can easily cause segfaults.

rewind t sets the lower bound of the window to the lower limit.

reset t sets the window to the limits.

flip_lo t sets the window to range from the lower limit to the lower bound of the old window. This is typically called after a series of Fills, to reposition the window in preparation to Consume the newly written data.

The bounded version narrows the effective limit. This can preserve some data near the limit, such as an hypothetical packet header, in the case of bounded_flip_lo or unfilled suffix of a buffer, in bounded_flip_hi.

compact t copies data from the window to the lower limit of the iobuf and sets the window to range from the end of the copied data to the upper limit. This is typically called after a series of Consumes to save unread data and prepare for the next series of Fills and flip_lo.

flip_hi t sets the window to range from the the upper bound of the current window to the upper limit. This operation is dual to flip_lo and is typically called when the data in the current (narrowed) window has been processed and the window needs to be positioned over the remaining data in the buffer. For example: 

      (* ... determine initial_data_len ... *)
      Iobuf.resize buf ~len:initial_data_len;
      (* ... and process initial data ... *)
      Iobuf.flip_hi buf;

Now the window of buf ranges over the remainder of the data.

protect_window_and_bounds t ~f applies f to t and restores t's bounds afterwards.

Getting and setting data



"consume" and "fill" functions access data at the lower bound of the window and advance lower bound of the window. "peek" and "poke" functions access data but do not advance the window.

to_string t returns the bytes in t as a string. It does not alter the window.

to_string_hum t produces a readable, multi-line representation of an iobuf. bounds defaults to `Limits and determines how much of the contents are shown.

Consume.string t ~len reads len characters (all, by default) from t into a new string and advances the lower bound of the window accordingly.

Consume.bin_prot X.bin_read_t t returns the initial X.t in t, advancing past the bytes read.

To_string.blito ~src ~dst ~dst_pos ~src_len () reads src_len bytes from src, advancing src's window accordingly, and writes them into dst starting at dst_pos. By default dst_pos = 0 and src_len = length src. It is an error if dst_pos and src_len don't specify a valid region of dst or src_len > length src.

Fill.bin_prot X.bin_write_t t x writes x to t in bin-prot form, advancing past the bytes written.

Peek and Poke functions access a value at pos from the lower bound of the window and do not advance.

Peek.bin_prot X.bin_read_t t returns the initial X.t in t without advancing.

Following the bin_prot protocol, the representation of x is X.bin_size_t x bytes long. Peek., Poke., Consume., and Fill.bin_prot do not add any size prefix or other framing to the bin_prot representation.

Similar to Consume.To_*, but do not advance the buffer.

Poke.bin_prot X.bin_write_t t x writes x to the beginning of t in binary form without advancing. You can use X.bin_size_t to tell how long it was. X.bin_write_t is only allowed to write that portion of the buffer to which you have access.

decimal t ~pos i returns the number of bytes written at pos.

Unsafe has submodules that are like their corresponding module, except with no range checks. Hence, mistaken uses can cause segfaults. Be careful!

fill_bin_prot writes a bin-prot value to the lower bound of the window, prefixed by its length, and advances by the amount written. fill_bin_prot returns an error if the window is too small to write the value.

consume_bin_prot t reader reads a bin-prot value from the lower bound of the window, which should have been written using fill_bin_prot, and advances the window by the amount read. consume_bin_prot returns an error if there is not a complete message in the window and in that case the window is left unchanged.

Don't use these without a good reason, as they are incompatible with similar functions in Reader and Writer. They use a 4-byte length rather than an 8-byte length.

Blit copies between iobufs and advances neither src nor dst.

Override types of sub and subo to allow return type to have seek as needed.

Blit_consume copies between iobufs and advances src but does not advance dst.

Blit_fill copies between iobufs and advances dst but does not advance src.

Blit_consume_and_fill copies between iobufs and advances both src and dst.

I/O



Iobuf has analogs of various Bigstring functions. These analogs advance by the amount written/read.

Expert



The Expert module is for building efficient out-of-module Iobuf abstractions.

They will not allocate, and are mainly here to assist in building low-cost syscall wrappers.

One must be careful to avoid writing out of the limits (between lo_min and hi_max) of the buf. Doing so would violate the invariants of the parent Iobuf.