Kotlin 官方参考文档 中文版

 主页   资讯   文章   代码 

Kotlin/Native 中的并发

Kotlin/Native runtime doesn't encourage a classical thread-oriented concurrency
model with mutually exclusive code blocks and conditional variables, as this model is
known to be error-prone and unreliable. Instead, we suggest a collection of
alternative approaches, allowing you to use hardware concurrency and implement blocking IO.
Those approaches are as follows, and they will be elaborated on in further sections:

  • Workers with message passing
  • Object subgraph ownership transfer
  • Object subgraph freezing
  • Object subgraph detachment
  • Raw shared memory using C globals
  • Coroutines for blocking operations (not covered in this document)

Workers

Instead of threads Kotlin/Native runtime offers the concept of workers: concurrently executed
control flow streams with an associated request queue. Workers are very similar to the actors
in the Actor Model. A worker can exchange Kotlin objects with another worker, so that at any moment
each mutable object is owned by a single worker, but ownership can be transferred.
See section Object transfer and freezing.

Once a worker is started with the Worker.start function call, it can be addressed with its own unique integer
worker id. Other workers, or non-worker concurrency primitives, such as OS threads, can send a message
to the worker with the execute call.

```kotlin val future = execute(TransferMode.SAFE, { SomeDataForWorker() }) { // data returned by the second function argument comes to the // worker routine as 'input' parameter. input -> // Here we create an instance to be returned when someone consumes result future. WorkerResult(input.stringParam + " result") } future.consume { // Here we see result returned from routine above. Note that future object or // id could be transferred to another worker, so we don't have to consume future // in same execution context it was obtained. result -> println("result is $result") } ```

The call to execute uses a function passed as its second parameter to produce an object subgraph
(i.e. set of mutually referring objects) which is then passed as a whole to that worker, it is then no longer
available to the thread that initiated the request. This property is checked if the first parameter
is TransferMode.SAFE by graph traversal and is just assumed to be true, if it is TransferMode.UNSAFE.
The last parameter to execute is a special Kotlin lambda, which is not allowed to capture any state,
and is actually invoked in the target worker's context. Once processed, the result is transferred to whatever consumes
it in the future, and it is attached to the object graph of that worker/thread.

If an object is transferred in UNSAFE mode and is still accessible from multiple concurrent executors,
program will likely crash unexpectedly, so consider that last resort in optimizing, not a general purpose
mechanism.

For a more complete example please refer to the workers example
in the Kotlin/Native repository.

Object transfer and freezing

An important invariant that Kotlin/Native runtime maintains is that the object is either owned by a single
thread/worker, or it is immutable (shared XOR mutable). This ensures that the same data has a single mutator, and so there is no need for locking to exist. To achieve such an invariant, we use the concept of not externally referred object subgraphs.
This is a subgraph which has no external references from outside of the subgraph, which could be checked
algorithmically with O(N) complexity (in ARC systems), where N is the number of elements in such a subgraph.
Such subgraphs are usually produced as a result of a lambda expression, for example some builder, and may not
contain objects, referred to externally.

Freezing is a runtime operation making a given object subgraph immutable, by modifying the object header
so that future mutation attempts throw an InvalidMutabilityException. It is deep, so
if an object has a pointer to other objects - transitive closure of such objects will be frozen.
Freezing is a one way transformation, frozen objects cannot be unfrozen. Frozen objects have a nice
property that due to their immutability, they can be freely shared between multiple workers/threads
without breaking the "mutable XOR shared" invariant.

If an object is frozen it can be checked with an extension property isFrozen, and if it is, object sharing
is allowed. Currently, Kotlin/Native runtime only freezes the enum objects after creation, although additional
autofreezing of certain provably immutable objects could be implemented in the future.

Object subgraph detachment

An object subgraph without external references can be disconnected using DetachedObjectGraph<T> to
a COpaquePointer value, which could be stored in void* data, so the disconnected object subgraphs
can be stored in a C data structure, and later attached back with DetachedObjectGraph<T>.attach() in an arbitrary thread
or a worker. Combining it with raw memory sharing it allows side channel object transfer between
concurrent threads, if the worker mechanisms are insufficient for a particular task.

Raw shared memory

Considering the strong ties between Kotlin/Native and C via interoperability, in conjunction with the other mechanisms
mentioned above it is possible to build popular data structures, like concurrent hashmap or shared cache with
Kotlin/Native. It is possible to rely upon shared C data, and store in it references to detached object subgraphs.
Consider the following .def file:

```c package = global --- typedef struct { int version; void* kotlinObject; } SharedData; SharedData sharedData; ```

After running the cinterop tool it can share Kotlin data in a versionized global structure,
and interact with it from Kotlin transparently via autogenerated Kotlin like this:

```kotlin class SharedData(rawPtr: NativePtr) : CStructVar(rawPtr) { var version: Int var kotlinObject: COpaquePointer? } ```

So in combination with the top level variable declared above, it can allow looking at the same memory from different
threads and building traditional concurrent structures with platform-specific synchronization primitives.

Global variables and singletons

Frequently, global variables are a source of unintended concurrency issues, so Kotlin/Native implements
the following mechanisms to prevent the unintended sharing of state via global objects:

  • global variables, unless specially marked, can be only accessed from the main thread (that is, the thread
    Kotlin/Native runtime was first initialized), if other thread access such a global, IncorrectDereferenceException is thrown
  • for global variables marked with the @kotlin.native.ThreadLocal annotation each threads keeps thread-local copy,
    so changes are not visible between threads
  • for global variables marked with the @kotlin.native.SharedImmutable annotation value is shared, but frozen
    before publishing, so each threads sees the same value
  • singleton objects unless marked with @kotlin.native.ThreadLocal are frozen and shared, lazy values allowed,
    unless cyclic frozen structures were attempted to be created

  • enums are always frozen

    Combined, these mechanisms allow natural race-freeze programming with code reuse across platforms in MPP projects.