From: Andy Kosela <akosela@andykosela.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] UVM VM system
Date: Sun, 2 Sep 2018 08:29:42 +0200 [thread overview]
Message-ID: <CALMnNGhtP3fvGNHJ2XFmiVUGhRpjQRAViHLE4yi+zB-StJdUdg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2OXVo0ng5bnpjVO_uLRLqGo3ROxhCNdJaTmr8qa3Nb_EQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Saturday, September 1, 2018, Clem Cole <clemc@ccc.com> wrote:
>
>
>
>>
>> Has FreeBSD considered this?
>>
> Last I knew, no. I was under the impression, the work FreeBSD did
> rewriting the Mach stuff paid off for them at the time. I have FreeBSD,
> OpenBSD and Linux (and Mac OSx) all running on my systems here. But the
> problem is that the HW is all over the map in termns of release date, so
> I'm not sure which is faster at this point. The *BSD systems are the
> easiest to admin and clean/simplest (which is why they only systems I have
> exposed is an OpenBSD box).
>
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
--Andy
[-- Attachment #2: Type: text/html, Size: 1339 bytes --]
next prev parent reply other threads:[~2018-09-02 6:30 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 [this message]
2018-09-02 8:07 ` Steve Mynott
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=CALMnNGhtP3fvGNHJ2XFmiVUGhRpjQRAViHLE4yi+zB-StJdUdg@mail.gmail.com \
--to=akosela@andykosela.com \
--cc=clemc@ccc.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).