The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] UVM VM system
Date: Sat, 1 Sep 2018 11:50:53 -0700	[thread overview]
Message-ID: <20180901185053.GA20993@mcvoy.com> (raw)

So I just read this

https://www.usenix.org/legacy/event/usenix99/full_papers/cranor/cranor.pdf

and it looks encouraging.  Apparently NetBSD is using it.  Does anyone
know if they are happy with it?

Has FreeBSD considered this?

Has anyone benchmarked FreeBSD against NetBSD to see which is faster
for VM stuff?

             reply	other threads:[~2018-09-01 18:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-01 18:50 Larry McVoy [this message]
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

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=20180901185053.GA20993@mcvoy.com \
    --to=lm@mcvoy.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).