From owner-freebsd-current@FreeBSD.ORG Fri Jan 16 09:20:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3F2516A4CE for ; Fri, 16 Jan 2004 09:20:16 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 53DF543D60 for ; Fri, 16 Jan 2004 09:20:11 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 26968 invoked by uid 1002); 16 Jan 2004 17:20:08 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 16 Jan 2004 17:20:08 -0000 Message-ID: <40081CDB.7040503@freebsd.org> Date: Fri, 16 Jan 2004 10:18:19 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joan Picanyol References: <200401151316.24827.eqe@cox.net> <20040116084230.Y92448@carver.gumbysoft.com> <20040116165232.GA13397@grummit.biaix.org> In-Reply-To: <20040116165232.GA13397@grummit.biaix.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: SMP and one-process threads X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2004 17:20:16 -0000 Joan Picanyol wrote: > * Doug White [20040116 17:41]: > >>Be careful.... FreeBSD doesn't currently schedule different threads of the >>same program on different processors. > > Is this true no matter of scheduler/libmap.conf combination? Is it a > planned/required feature? > > qvb > -- > pica Doug's statement was a bit too absolute. The default threading package is libc_r, which is purely a userland threading package and does not allow threads to be scheduled on concurrent CPUs. libkse does allow this, and can be enabled be either linking directly to it, or using the libmap.conf(5) facility. Scott