From owner-freebsd-arm@FreeBSD.ORG Mon Dec 22 14:56:53 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 46C46ADD for ; Mon, 22 Dec 2014 14:56:53 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1.freebsd.org (Postfix) with ESMTP id 32AF65ED for ; Mon, 22 Dec 2014 14:56:52 +0000 (UTC) Received: from msam.nabble.com (unknown [162.253.133.85]) by mwork.nabble.com (Postfix) with ESMTP id 167A9E72F0B for ; Mon, 22 Dec 2014 06:56:53 -0800 (PST) Date: Mon, 22 Dec 2014 07:56:51 -0700 (MST) From: Scott Ellis To: freebsd-arm@freebsd.org Message-ID: <1419260211677-5975286.post@n5.nabble.com> Subject: PANDABOARD default scheduler MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2014 14:56:53 -0000 Why does the PANDABOARD kernel config default to SCHED_4BSD instead of SCHED_ULE? It's a dual-core board. Just curious. SCHED_ULE has been working fine for me on a similar OMAP4 board. -- View this message in context: http://freebsd.1045724.n5.nabble.com/PANDABOARD-default-scheduler-tp5975286.html Sent from the freebsd-arm mailing list archive at Nabble.com.