From owner-freebsd-arch Sat Jan 25 18:18:50 2003 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 B467637B401; Sat, 25 Jan 2003 18:18:49 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E72543F1E; Sat, 25 Jan 2003 18:18:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.6/8.12.6) with ESMTP id h0Q2Il0i024484; Sat, 25 Jan 2003 18:18:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.6/8.12.6/Submit) id h0Q2IlkX024483; Sat, 25 Jan 2003 18:18:47 -0800 (PST) Date: Sat, 25 Jan 2003 18:18:47 -0800 (PST) From: Matthew Dillon Message-Id: <200301260218.h0Q2IlkX024483@apollo.backplane.com> To: Steve Kargl Cc: Jeff Roberson , Robert Watson , Gary Jennejohn , arch@FreeBSD.ORG Subject: Re: New scheduler (#3) References: <20030125171217.D18109-100000@mail.chesapeake.net> <200301252320.h0PNKVoq090077@apollo.backplane.com> <200301252350.h0PNo6xO009489@apollo.backplane.com> <200301260114.h0Q1EXuu017546@apollo.backplane.com> <20030126013234.GA19891@troutmask.apl.washington.edu> 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 :This would explain why my recent effort to force Jeff's :scheduler to overload without X running didn't work. : :Matt, are you generating patches or simply analyzing :Jeff's code? I don't mind panicking my machine if you :need a guinea pig. : :-- :Steve I'm just analyzing Jeff's code and doing simple rip-up tests. I haven't been saving the bug fixes. Mainly I am getting up to speed on the scheduler API so I can implement my fractional fair share cpu and I/O scheduler down the line. I expect Jeff can fix the more obvious bugs in a few seconds. Dealing with the cpu-thread-stealing issue is a much harder problem. I saw the flip-flop and reported it, but did not try to fix it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message