Date: Mon, 30 Dec 2002 16:20:16 -0800 From: David Schultz <dschultz@uclink.Berkeley.EDU> To: Ken Menzel <kenm@icarz.com> Cc: Aaron Wohl <freebsd@soith.com>, freebsd-stable@FreeBSD.ORG Subject: Re: MAXDSIZ and pthreads large ram etc Message-ID: <20021231002016.GA2188@HAL9000.homeunix.com> In-Reply-To: <013c01c2b043$f6448be0$ecdb7bd1@kenxp> References: <20021224215413.B597F17A32@www.fastmail.fm> <200212242312.gBONCjqD044717@apollo.backplane.com> <013c01c2b043$f6448be0$ecdb7bd1@kenxp>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Ken Menzel <kenm@icarz.com>: > I first saw this problem about two years ago when MAXDSIZ was made > tunable in the loader. Now any value over MAXDSIZ="(2047*1024*1024)" > causes a threaded program to SIGABRT. (This is the the value I use). > I had tracked it down to the exact set of changes but could not > identify what caused it, and 2G is OK for me so I did not pursue it. > Like Matt Says you real limit is 3G anyway and memory addressing above > 4G has been discussed in other threads (see the archives). > > I used to be able to set MAXDSIZE to 3000. Anyway if you are > interested in trying to track down exact cause I did save the commit > that caused it and I can rollback to before the change and see it > fixed then apply the set of changes. It was a very large commit dated > Date: Fri, 2 Nov 2001 17:41:10 -0800 (PST), by Paul Saab. This sounds like a sign bug in the code that maps the thread stacks in the pthreads code. In -CURRENT, the code to do this is quite different (and fixes at least one other problem). It would be interesting to see if the new code addresses your problem. Perhaps it could be MFC'd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021231002016.GA2188>