From owner-freebsd-smp Wed Aug 22 13:39:49 2001 Delivered-To: freebsd-smp@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id B9C0B37B425; Wed, 22 Aug 2001 13:39:42 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f7MKdeW78135; Wed, 22 Aug 2001 13:39:40 -0700 (PDT) (envelope-from dillon) Date: Wed, 22 Aug 2001 13:39:40 -0700 (PDT) From: Matt Dillon Message-Id: <200108222039.f7MKdeW78135@earth.backplane.com> To: Bruce Evans Cc: Terry Lambert , Jake Burkholder , John Baldwin , , Subject: Re: Preliminary proposed rollup of kernel submap initialization code References: <20010823060618.M15348-100000@besplex.bde.org> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org :> All the fields are related. They belong in a structure rather then :> as free globals or free statics. And it makes it easier for the MD :> code to call the MI code. My opinion, anyway. : :Actually, they are even less related than at first appearance. :buffer_sva, buffer_eva, pager_sva and pager_eva aren't really used. :They are just places for throwing away the values returned indirectly :by kmem_suballoc(). clean_sva and clean_eva are used in one place in :pmap.c. : :Bruce Look, I don't want to get into a big argument. It makes sense to keep them together because they are related, and even though our existing platforms do not appear to need them I can see that changing in the future as we add more platform ports to the system. For example, having the pager range accessible could be advantageous for platforms that take TLB faults. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message