From owner-freebsd-current Tue Jul 13 1:34:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 49FE614BF4 for ; Tue, 13 Jul 1999 01:34:35 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id LAA09881; Tue, 13 Jul 1999 11:29:05 +0300 (EEST) (envelope-from will) To: Alan Cox Cc: current@freebsd.org Subject: Re: Thread stack allocation (was Re: cvs commit: src/lib/libc_r Makefile src/lib/libc_r/uthread pthread_private.h uthread_create.c uthread_gc.c uthread_init.c) References: <199907121853.WAA27876@arc.hq.cti.ru> <19990713023012.K6401@cs.rice.edu.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 13 Jul 1999 11:29:03 +0300 In-Reply-To: Alan Cox's message of "13 Jul 1999 10:32:41 +0300" Message-ID: <86673p7y28.fsf@not.demophon.com> Lines: 22 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alan Cox writes: > P.S. As an aside, just once, everyone should look at the /proc/"pid"/map > of a running cvsup. Each line you see is a vm_map_entry. (What you > see is a result of Modula-3's garbage collector.) Roughly speaking, Modula-3 really appears to be doing something weird, making half of the entries read-only. A garbage collected language should actually be capable of doing a better job than a non-gc one. > on a page fault, if we're not faulting on the same range of addresses > as the last page fault, a linear cost search is performed > to find the correct entry. Are you suggesting that vm_map_entries should be in, say, a red-black tree (not a bad idea, I've done this), or that programs should just keep their memory contiguous ((s)brk rather than mmap)? The latter is becoming increasingly difficult with the large numbers of shared libraries and growing use of dynamically loaded internal modules (XFree86 4.0?). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message