From owner-freebsd-hackers Thu Apr 8 14:32:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 379B615717 for ; Thu, 8 Apr 1999 14:32:08 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id OAA91967; Thu, 8 Apr 1999 14:27:56 -0700 (PDT) Date: Thu, 8 Apr 1999 14:27:53 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: "John S. Dyson" , freebsd-hackers@FreeBSD.ORG Subject: Re: scheduling queues in FreeBSD In-Reply-To: <199904082021.NAA14426@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG not sure I follow.. going ot the meeting tonight? maybe I can get you to explain better there.. julian On Thu, 8 Apr 1999, Matthew Dillon wrote: > :Matthew Dillon said: > :> > :> The 'idle' and 'realtime' queues were hacked in I don't know when, but > :> they don't work very well... there are a number of situations that can > :> cause machine lockups. Frankly, I'd like to see both ripped out completely > :> and a better solution put in later on. > :> > :I agree -- they create messy LL code, and as you say, just don't work correctly. > :-- > :John | Never try to teach a pig to sing, > :dyson@iquest.net | it makes one look stupid > :jdyson@nc.com | and it irritates the pig. > > One thing we could do that would accomplish virtually the same goals would > be to 'lock' the cpu priority. This would be a great temporary solution. > > If the cpu priority is locked into queue 0, we are effectively equivalent > to the idle queue. If the cpu priority is locked into queue 31, we are > effectively equivalent to the realtime queue. We then reduce the > priority range that 'normal' processes are allowed to obtain such that they > fall into queues 1-30. Poof, done. > > -Matt > Matthew Dillon > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message