From owner-freebsd-alpha Thu Oct 5 16:45:21 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id C5AE737B503 for ; Thu, 5 Oct 2000 16:45:18 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 13hKhJ-000Ja8-0K; Thu, 5 Oct 2000 23:45:13 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id AAA19068; Fri, 6 Oct 2000 00:51:19 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 6 Oct 2000 00:44:34 +0100 (BST) From: Doug Rabson To: Terry Lambert Cc: Wilko Bulte , Matthew Jacob , FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <200010052209.PAA16408@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 5 Oct 2000, Terry Lambert wrote: > > > Do you know *if* there is a hard limit at 2Gb? > > > > I don't think there is a *hard* limit for the basic VM system but I > > imagine it might have problems finding a large enough contiguous region to > > map the vm_page_t structures. The main limitation is in the i/o system as > > previously noted. > > It seems to me that the contiguity requirement is bogus. > > If contiguity is other than an implementation artificat (i.e. > it is a true hardware requirement), then it seems to me that > it is time to provide a mechanism for defragging KVA space, > or place the vm_page_t structures in a seperate virtual > address space. The vm_page_t's are initialised *very* early and are generally mapped by a very simple subset of pmap. Currently, the VM system assumes that it can map a single contiguous physical extent for them although it could conceivably be slightly smarter. > > On a related note, I've always though that drivers (and their > related kernel threads, should such obnoxious things become > more commonplace) ought to run in their own VA space, on a > per driver basis, so that a bad driver couldn't pee in the > pool. This would keep bad drivers from actually crashing > the system, short of a halt or going into a tight loop (even > then, a timer interrupt should be able to recover the halt, > and a preemption should be able to recover the loop, if it > is a kernel thread -- or even generally, if kernel preemption > were to be supported). This would probably waste far too much performance to be actually useful. On the other hand, there are OSs which do this so perhaps the cost is manageable. Much too hard to implement within the existing kernel infrastructure though. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message