From owner-freebsd-stable@FreeBSD.ORG Fri Nov 19 01:05:19 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 041E9106566B; Fri, 19 Nov 2010 01:05:19 +0000 (UTC) (envelope-from dmagda@ee.ryerson.ca) Received: from eccles.ee.ryerson.ca (ee.ryerson.ca [141.117.1.2]) by mx1.freebsd.org (Postfix) with ESMTP id B19838FC17; Fri, 19 Nov 2010 01:05:18 +0000 (UTC) Received: from [10.0.1.3] (bas1-toronto09-1279534875.dsl.bell.ca [76.68.39.27]) (authenticated bits=0) by eccles.ee.ryerson.ca (8.14.4/8.14.4) with ESMTP id oAJ0owe8008179 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 18 Nov 2010 19:50:59 -0500 (EST) (envelope-from dmagda@ee.ryerson.ca) Message-Id: <38521DB9-B3AE-4F96-89C9-75A80D2E0B3E@ee.ryerson.ca> From: David Magda To: Julian Elischer In-Reply-To: <4CE5BA37.20604@freebsd.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Thu, 18 Nov 2010 19:50:58 -0500 References: <4CE50849.106@zedat.fu-berlin.de> <4CE52177.3020306@freebsd.org> <20101118182324.GA36312@freebsd.org> <20101118182852.GR63683@over-yonder.net> <20101118185635.GA43706@freebsd.org> <20101118170623.7f9c14f3@kan.dnsalias.net> <20101118233731.GA10392@freebsd.org> <4CE5BA37.20604@freebsd.org> X-Mailer: Apple Mail (2.936) Cc: freebsd-performance@freebsd.org, Current , FreeBSD Stable Subject: Re: TTY task group scheduling X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 01:05:19 -0000 On Nov 18, 2010, at 18:43, Julian Elischer wrote: > we are part of the way there.. > > at least we did abstract the scheduler to the point where we have > two completely different ones. you are welcome to develop a > 'framework as you describe and plug it into the abstraction we > already have. It may be something to suggest for the next round of Google's Summer of Code. Or perhaps part of a school project in operating systems work (master's level? eager-beaver bachelor's thesis?). Having a bit more flexibility in being able to make different components "pluggable" would help encourage the use of BSD in more research projects. And more people learning and hacking on BSD can't be a bad thing. :)