polytypic

Support for FLS in the OCaml runtime

---

OCaml multicore architecture

• DLS = Domain Local Storage
• TLS = Thread Local Storage
• FLS = Fiber Local Storage

polytypic

Every time I look at ocaml/ocaml code for more than a few seconds, I spot issues. This collects some of them. Some day I'll just learn to shrug and move on.

polytypic

polytypic

Picos — Interoperable effects based concurrency

https://github.com/ocaml-multicore/picos

What is Picos?

• It is an interface:

  Libraries & Applications          '' Schedulers ''

polytypic

Fear the Obj.magic

Let me first quote a paragraph from the Memory Representation of Values (with my emphasis):

Obj is an undocumented module that exposes the internals of the OCaml compiler and runtime. It is very useful for

polytypic

A lock-free starvation avoiding bag

module type Bag = sig
  type 'a t
  val create : unit -> 'a t
  val to_list : 'a t -> 'a list
  type 'a handle
  val add : 'a t -> 'a -> 'a handle
  val remove : 'a t -> 'a handle -> unit

polytypic

Currently OCaml 5 provides a Domain.DLS module for domain-local storage.

Unfortunately,

1. there is no corresponding Thread.TLS for (sys)thread-local storage, and

2. the current implementation of Domain.DLS is not thread-safe.

polytypic

For a long time OCaml has supported lightweight threads exposed via the Thread module. These threads are often called “systhreads”, but I will simply call them “threads” in this post.

The OCaml Stdlib also provides many mutable data structures such as Hashtbl, Queue, and Stack. As the documentation alerts, none of these are thread-safe.

polytypic

A pattern for using GADTs to subset cases

Consider the following straightforward mutable queue implementation using two stacks:

type 'a adt_queue = {
  mutable head : 'a head;
  mutable tail : 'a tail;
}

polytypic

(* Copyright (c) 2023 Vesa Karvonen

   Permission to use, copy, modify, and/or distribute this software for any
   purpose with or without fee is hereby granted, provided that the above
   copyright notice and this permission notice appear in all copies.

   THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
   REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
   AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
   INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM