From: Steve Mynott <steve.mynott@gmail.com>
To: Andy Kosela <akosela@andykosela.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] UVM VM system
Date: Sun, 2 Sep 2018 09:07:02 +0100 [thread overview]
Message-ID: <20180902080701.i5juplmwihwtppnp@zippy.shellcode.eu> (raw)
In-Reply-To: <CALMnNGhtP3fvGNHJ2XFmiVUGhRpjQRAViHLE4yi+zB-StJdUdg@mail.gmail.com>
On Sun, Sep 02, 2018 at 08:29:42AM +0200, Andy Kosela typed:
> OpenBSD is also using uvm[1]. But these days it certainly differs from
> NetBSD implementation as it was hacked on by different people during the
> last several years.
>
> [1] https://man.openbsd.org/uvm.9
Both forks now include a unified buffer cache.
There is an interesting series of blog posts at
<http://blog.pr4tt.com/2016/02/02/BSD-virtual-memory/>
The OpenBSD UVM has particularly diverged from the original with the
addition of a "dead entry queue" and the blog author complains about its
lack of documentation. He also mentions an experimental RadixVM as
being current "state of the art" although its not available on any
mainstream systems.
--
Steve Mynott <steve.mynott@gmail.com>
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5
prev parent reply other threads:[~2018-09-02 8:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 18:50 Larry McVoy
2018-09-01 19:07 ` Warner Losh
2018-09-01 19:16 ` Clem Cole
2018-09-01 19:41 ` ron minnich
2018-09-01 19:45 ` ron minnich
2018-09-01 20:25 ` Warner Losh
2018-09-01 21:15 ` ron minnich
2018-09-02 5:19 ` Kevin Bowling
2018-09-02 14:55 ` Warner Losh
2018-09-02 15:28 ` Will Senn
2018-09-01 19:53 ` Brad Spencer
2018-09-02 6:29 ` Andy Kosela
2018-09-02 8:07 ` Steve Mynott [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180902080701.i5juplmwihwtppnp@zippy.shellcode.eu \
--to=steve.mynott@gmail.com \
--cc=akosela@andykosela.com \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).