From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 8 11:06:59 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AD2D106564A for ; Wed, 8 Feb 2012 11:06:59 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id E5EC58FC17 for ; Wed, 8 Feb 2012 11:06:58 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Rv5MX-0003cX-Dy for freebsd-hackers@freebsd.org; Wed, 08 Feb 2012 12:06:57 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 08 Feb 2012 12:06:57 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 08 Feb 2012 12:06:57 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Wed, 08 Feb 2012 12:06:47 +0100 Lines: 18 Message-ID: References: <4F2F7B7F.40508@FreeBSD.org> <20120206160136.GA35918@freebsd.org> <4F2FFFDA.2080608@FreeBSD.org> <201202061837.48946.tijl@coosemans.org> <4F301406.7080906@FreeBSD.org> <20120206191031.GA76990@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120110 Thunderbird/9.0 In-Reply-To: <20120206191031.GA76990@freebsd.org> Subject: Re: [RFT][patch] Scheduling for HTT and not only X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2012 11:06:59 -0000 On 06/02/2012 20:10, Alexander Best wrote: > btw: does anybody know, if there are plans to commit the BFS scheduler to HEAD BFS is available but I think it needs more work on it before it can be useful; it didn't explore some optimizations it could have and currently spends much more time in lock contention with itself that necessary. I.e. it's usable only in very borderline cases. > algorithm would be a scheduling infrastructure similar to GEOM. that way it > would be much easier to implement new algorithms (maybe in XML). I don't think XML would be applicable beyond fine-tuning an already existing scheduler (unless we implement a whole Turing-complete sublanguage in it :) ). Someone mentioned on a list that he has a "pluggable scheduler" infrastructure ready - this would be a necessary first step in modularization.