From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id e79b7f7f for ; Wed, 26 Jun 2019 19:40:32 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id D08639BF80; Thu, 27 Jun 2019 05:40:30 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 1B6B69BD84; Thu, 27 Jun 2019 05:40:09 +1000 (AEST) Received: by minnie.tuhs.org (Postfix, from userid 112) id E03409BD84; Thu, 27 Jun 2019 05:40:07 +1000 (AEST) X-Greylist: delayed 591 seconds by postgrey-1.36 at minnie.tuhs.org; Thu, 27 Jun 2019 05:40:07 AEST Received: from yagi.h-net.msu.edu (yagi.h-net.msu.edu [35.9.18.40]) by minnie.tuhs.org (Postfix) with ESMTP id 73E079BC77 for ; Thu, 27 Jun 2019 05:40:07 +1000 (AEST) Received: from yagi.h-net.org (unknown [127.0.0.1]) by yagi.h-net.msu.edu (Postfix) with ESMTP id DBB731D33AD for ; Wed, 26 Jun 2019 15:30:15 -0400 (EDT) X-Virus-Scanned: amavisd-new at example.com Received: from yagi.h-net.msu.edu ([127.0.0.1]) by yagi.h-net.org (yagi.h-net.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UYwilreNnP2G for ; Wed, 26 Jun 2019 15:30:06 -0400 (EDT) Received: from yagi.h-net.org (localhost [127.0.0.1]) by yagi.h-net.msu.edu (Postfix) with ESMTP for ; Wed, 26 Jun 2019 15:30:05 -0400 (EDT) References: <34DB62C2-7D8C-468B-99E1-CA035C9141A2@eschatologist.net> <5df8c6f6-2768-4bfb-9c47-3345098078a7@PU1APC01FT048.eop-APC01.prod.protection.outlook.com> <20190625000630.GA7655@mcvoy.com> <20190625003120.GA28608@mit.edu> <20190625004523.GB7655@mcvoy.com> <20190626024503.GA43970@wopr> <20190626025646.GR925@mcvoy.com> <20190626151143.GC3116@mit.edu> <20190626174431.GT925@mcvoy.com> To: tuhs@minnie.tuhs.org From: Dennis Boone In-reply-to: (Your message of Wed, 26 Jun 2019 12:22:42 -0700.) <34DB62C2-7D8C-468B-99E1-CA035C9141A2@eschatologist.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <30365.1561577405.1@yagi.h-net.org> Content-Transfer-Encoding: 8bit Date: Wed, 26 Jun 2019 15:30:05 -0400 Message-Id: <20190626193015.DBB731D33AD@yagi.h-net.msu.edu> Subject: Re: [TUHS] CMU Mach sources? X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" > For another example, Mach did a lot of extra work around things like > processor sets that wouldn’t be needed on (say) a dual-CPU > shared-cache uniform-memory systems, but turns out to be important > when dealing with things like systems with a hierarchy of CPUs, > caches, and memories. Did they know about all the possible needs for > that before they started? For example, our campus had one of these, with 96 processors if I recall correctly. Mach-based OS. https://en.wikipedia.org/wiki/BBN_Butterfly De