From owner-freebsd-hackers Wed Apr 7 23:51:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E5D4015873 for ; Wed, 7 Apr 1999 23:51:37 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA08733; Wed, 7 Apr 1999 23:49:36 -0700 (PDT) (envelope-from dillon) Date: Wed, 7 Apr 1999 23:49:36 -0700 (PDT) From: Matthew Dillon Message-Id: <199904080649.XAA08733@apollo.backplane.com> To: Mohit Aron Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: scheduling queues in FreeBSD References: <199904080401.XAA07250@cs.rice.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : I'm using FreeBSD-2.2.6. It seems that the scheduler maintains :more than 1 queue for process scheduling - whichqs, whichrtqs, ... Can someone :please tell me the significance of all these queues. Also which processes :go in which queues. Thanks, : : :- Mohit The scheduler has a notion of an 'idle', 'normal', and 'realtime' process queue. Unless you do something explicitly, all processes on the system are going to be on the 'normal' queue. i.e. 'whichqs'. 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. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message