From: Clem Cole <clemc@ccc.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] UVM VM system
Date: Sat, 1 Sep 2018 15:16:42 -0400 [thread overview]
Message-ID: <CAC20D2OXVo0ng5bnpjVO_uLRLqGo3ROxhCNdJaTmr8qa3Nb_EQ@mail.gmail.com> (raw)
In-Reply-To: <20180901185053.GA20993@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]
On Sat, Sep 1, 2018 at 2:51 PM Larry McVoy <lm@mcvoy.com> wrote:
> So I just read this
>
> https://www.usenix.org/legacy/event/usenix99/full_papers/cranor/cranor.pdf
I remember that presentsation, it was exciting and very cool ;-)
>
>
> and it looks encouraging. Apparently NetBSD is using it.
Hmm - integrated/used it at one time ... but ... I'm not sure of that is
still true of it it even really made it out. That was all happening when I
was still hacking on Alphas (which was a long time ago). We'd need the
active NetBSD folks to chime in on curent state.
> Does anyone
>
> know if they are happy with it?
>
At the time (and I'm doing this by memory) the buffer cache stuff needed a
rewrite which I thought FreeBSD did/was doing at the time.
In those days, FreeBSD was within epislon on of Tru64 on Alpha performance
and NetBSD had a ways to go. At the time, I gave a couple of Alphas to
somebody in the UK (I've forgotten whom); who was going to redo it.
>
> 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). But they have uses ;-)
>
> Has anyone benchmarked FreeBSD against NetBSD to see which is faster
> for VM stuff?
>
My data was from those days, and FreeBSD was winning, but thats a >>long<<
time ago. Lots of bits have been types into to the kernel of both systems,
so you tell me,
Clem
ᐧ
[-- Attachment #2: Type: text/html, Size: 4143 bytes --]
next prev parent reply other threads:[~2018-09-01 19:17 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 [this message]
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=CAC20D2OXVo0ng5bnpjVO_uLRLqGo3ROxhCNdJaTmr8qa3Nb_EQ@mail.gmail.com \
--to=clemc@ccc.com \
--cc=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).