From owner-freebsd-arch Wed Dec 6 14: 3: 2 2000 From owner-freebsd-arch@FreeBSD.ORG Wed Dec 6 14:02:59 2000 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 4870037B400; Wed, 6 Dec 2000 14:02:52 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB6LvHm16334; Wed, 6 Dec 2000 21:57:17 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB6M01t07697; Wed, 6 Dec 2000 22:00:01 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200012062200.eB6M01t07697@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Daniel Eischen Cc: Brian Somers , Robert Watson , freebsd-arch@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: Threads in the base system In-Reply-To: Message from Daniel Eischen of "Wed, 06 Dec 2000 16:50:29 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 22:00:01 +0000 From: Brian Somers Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 6 Dec 2000, Brian Somers wrote: > > Good spot. I believe NOLIBC_R should/must go. > > I was just [re]thinking about this. When we get libpthread (work > has just started on this), then libc_r will eventually go away. > It's not clear yet whether libpthread will exist as a separate > entity or whether it will evolve from libc_r. It's possible > that NOLIBC_R might actually become the default. We should really be advocating using threads in the base system rather than discouraging it (well, of course that's my view :-). I suspect however that to most people, libc_r is just some extra buildworld overhead.... I've already cast my vote, and can't see any strong argument not to remove NOLIBC_R (especially now that it breaks world :-) > > > Recently, pppctl was made thread-enabled, meaning that it relies on > > > libc_r. This makes the NOLIBC_R cannot be used with buildworld anymore. > > > Given that making pppctl depend on !NOLIBC_R may not be all that helpful, > > > it looks like we may need to lose NOLIBC_R. Presumably over time, threads > > > in default system applications will only become more popular. Any > > > thoughts (especially in light of upcoming KSE changes, which will make > > > threading integral to the system architecture)? > > > > > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > > > robert@fledge.watson.org NAI Labs, Safeport Network Services > > -- > Dan Eischen -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message