From owner-freebsd-current@FreeBSD.ORG  Thu Jul 10 11:04:10 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 88AED37B401
	for <current@freebsd.org>; Thu, 10 Jul 2003 11:04:10 -0700 (PDT)
Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2444743F75
	for <current@freebsd.org>; Thu, 10 Jul 2003 11:04:10 -0700 (PDT)
	(envelope-from julian@elischer.org)
Received: from interjet.elischer.org ([12.233.125.100])
          by attbi.com (rwcrmhc11) with ESMTP
          id <2003071018040401300gtkhae>; Thu, 10 Jul 2003 18:04:04 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA40879
	for <current@freebsd.org>; Thu, 10 Jul 2003 11:03:58 -0700 (PDT)
Date: Thu, 10 Jul 2003 11:03:56 -0700 (PDT)
From: Julian Elischer <julian@elischer.org>
To: FreeBSD current users <current@freebsd.org>
Message-ID: <Pine.BSF.4.21.0307101056420.40558-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: small scheduler hack/patch
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jul 2003 18:04:10 -0000


I have a small "proof of concept" scheduler hack at:
http://www.freebsd.org/~julian/it.diff

what it is supposed to do is check if there is an idle CPU at the time
that a thread is made runnable (assuming that idle CPUs are halted)
and if there is, it selects an idle CPU and gives it an IPI
to wake it up. (presumably it will then pick up the work).

It's only implemented for SMP/i386 as the code to halt the cpu is only
present (from my quick view) in x86 and it doesn't make sense in UP..

any comments and suggestions? (oh, and yes it's only in the 4bsd
scheduler.. I think jeff already handles this sort of thing).