From: Kevin Bowling <kevin.bowling@kev009.com>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] UVM VM system
Date: Sat, 1 Sep 2018 22:19:41 -0700 [thread overview]
Message-ID: <CAK7dMtBM6YhEPpsxwnvuZabcF6YVYTsx7jof4GQak6QcP2yh+g@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfogHqPr6GQ50y_8gVrhnNG-KxPWARuAoGHbKNOL_BKU6A@mail.gmail.com>
Seems like Chuck Cranor is at CMU http://chuck.cranor.org/. Chuck
Silvers is with you?
On Sat, Sep 1, 2018 at 1:25 PM, Warner Losh <imp@bsdimp.com> wrote:
>
>
> On Sat, Sep 1, 2018, 1:42 PM ron minnich <rminnich@gmail.com> wrote:
>>
>> I was his advisor on that thesis so I got to watch it roll out as it
>> happened.
>>
>> uvm replaced the machvm in netbsd.
>>
>> For a time, Chuck set it up to run in parallel with the existing VM. You
>> could start a process and pick which vm it used. For a while, it defaulted
>> to the existing one. Then, at some point, it defaulted to uvm. Then, at some
>> point, the old one was removed.
>>
>> more here:
>>
>> http://www.netbsd.org/docs/kernel/uvm.html
>>
>> via search terms
>> uvm replaces machvm netbsd
>>
>> chuck was a long time contributor to netbsd IIRC, but last time we talked,
>> he was using Linux.
>
>
> These days I know he's hacking on FreeBSD's storage stack with me at work
> :). I think he's still a netbsd contributor. I see his name in the commit
> log often..
>
> Warner
next prev parent reply other threads:[~2018-09-02 5:19 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 [this message]
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=CAK7dMtBM6YhEPpsxwnvuZabcF6YVYTsx7jof4GQak6QcP2yh+g@mail.gmail.com \
--to=kevin.bowling@kev009.com \
--cc=imp@bsdimp.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).