From owner-freebsd-arch Fri Sep 20 13:55: 3 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19FB837B401 for ; Fri, 20 Sep 2002 13:55:02 -0700 (PDT) Received: from 2-225.ctame701-1.telepar.net.br (2-225.ctame701-1.telepar.net.br [200.193.160.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7E6143E6E for ; Fri, 20 Sep 2002 13:55:00 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from localhost ([IPv6:::ffff:127.0.0.1]:27866 "EHLO localhost") by imladris.surriel.com with ESMTP id ; Fri, 20 Sep 2002 17:54:45 -0300 Date: Fri, 20 Sep 2002 17:54:43 -0300 (BRT) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: Julian Elischer Cc: Bill Huey , Subject: Re: New Linux threading model In-Reply-To: Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 20 Sep 2002, Julian Elischer wrote: > I didn't sat it's not possible, it's just that the interaction between > threads and KSEs on the run queue is very complicated in the current > "interim" scheduler (compatible with the old process scheduler but with > a huge "tumor" on the side of it to do something with threads) > ie. You need to schedule threads in the kernel, while not allowing > a process with a lot of threads to flood the system. Interesting problem, but that might be better done in a more generic way. Ie. first build a thread scheduler and then add support for generic resource containers that aren't tied to the thread<->process relation. Once you have that, you could substitute thread<->user for the default relationship and prevent users with many threads from flooding the CPU ;) Adding resource containers to a scheduler can be hard though, I still haven't found a pretty way of adding per-container (in my case I want to start with per-user) CPU time accounting to Ingo's O(1) scheduler. Sure, I've got several ugly ideas and one less ugly idea, but I haven't found anything nice yet... regards, Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://distro.conectiva.com/ Spamtraps of the month: september@surriel.com trac@trac.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message