Reword.
This commit is contained in:
parent
e624c3f0f8
commit
7154bcd65f
1 changed files with 1 additions and 2 deletions
|
@ -126,7 +126,7 @@ OCaml code compiles to native code running in the OCaml runtime, which is
|
|||
as performant as compiled C++ code. The OCaml runtime is just used for
|
||||
memory management, and very small compared to a JVM or Python runtime. As
|
||||
an example, our TLS library has up to 85% of the bulk throughput of OpenSSL (using
|
||||
AES128-CBC). The TLS handshake performance is equal with OpenSSL.
|
||||
AES128-CBC). The TLS handshake performance is comparable with OpenSSL.
|
||||
|
||||
### Dependency management
|
||||
|
||||
|
@ -136,7 +136,6 @@ network stack, the random number generator.
|
|||
Each of the services has multiple implementations that are chosen based on the target.
|
||||
On UNIX, the sockets API of the host is used as networking stack. On a
|
||||
unikernel, the TCP/IP stack natively implemented in OCaml is being used.
|
||||
|
||||
A MirageOS developer does not need to reason about compilation targets, just about the
|
||||
module interface.
|
||||
|
||||
|
|
Loading…
Reference in a new issue