From owner-freebsd-arch Thu Nov 22 20:35:12 2001 Delivered-To: freebsd-arch@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id F129E37B405; Thu, 22 Nov 2001 20:35:10 -0800 (PST) Received: from dialup-209.245.133.236.dial1.sanjose1.level3.net ([209.245.133.236] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16783P-00059Y-00; Thu, 22 Nov 2001 20:35:07 -0800 Message-ID: <3BFDD227.8F9A9540@mindspring.com> Date: Thu, 22 Nov 2001 20:35:51 -0800 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Marcel Moolenaar , John Baldwin , arch@FreeBSD.ORG Subject: Re: Kernel Thread scheduler References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Julian Elischer wrote: > > Interstingly only about 4 people downloaded all 7 pictures. > (according to the logs).. This is a bit disappointing. > Quite a few more looked at the first one, and then didn;t bother with the > rest.. I wonder if they had problems with it? was it impossible to look at > them for some people? Should I have done something different with them? > Or maybe the topic of shecduling thasks with multiple threads is just > boring :-) I am incredible disagreement about the idea of virtual processors (KSEG's), but then you know that from two years ago. It won't scale. There's no need to repeat everything ad infinitum, just because it's easier to implement. The resulting code is actually _less_ complex, though its conceptual complexity is higher. If you go don the virtual processor route, expect me to not ride in the bandwagon. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message