From: Will Senn <will.senn@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] UVM VM system
Date: Sun, 2 Sep 2018 10:28:36 -0500 [thread overview]
Message-ID: <82A3E3CE-2A86-4DDA-9C70-A2B6EE4872F7@gmail.com> (raw)
In-Reply-To: <CANCZdfpezckxXh5j2RO4K=W_Zq+eVGcsauC4h9sw4r+pZRe=YA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]
According to the Netbsd page:
Chuck Cranor designed and implemented UVM, Matthew Green handled integration issues and wrote the swap subsystem, Chuck Silvers wrote the anonymous memory object pager (which added support for shared memory), and various other developers have converted the appropriate ports across. Andrew Brown modified UVM to be able to do top down memory management.
It appears both Chuck’s contributed!
Will
Sent from my iPhone
> On Sep 2, 2018, at 9:55 AM, Warner Losh <imp@bsdimp.com> wrote:
>
>
>
>> On Sat, Sep 1, 2018, 11:19 PM Kevin Bowling <kevin.bowling@kev009.com> wrote:
>> Seems like Chuck Cranor is at CMU http://chuck.cranor.org/. Chuck
>> Silvers is with you?
>
>
> Why I'm embarrassed to admit you are right. Chuck Silvers also did some VM work, but not uvm.
>
> Warner
>
>> 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
[-- Attachment #2: Type: text/html, Size: 3633 bytes --]
next prev parent reply other threads:[~2018-09-02 15:29 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 [this message]
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=82A3E3CE-2A86-4DDA-9C70-A2B6EE4872F7@gmail.com \
--to=will.senn@gmail.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).