From owner-freebsd-current@FreeBSD.ORG Tue Apr 8 07:28:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4BEF37B401 for ; Tue, 8 Apr 2003 07:28:17 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DF1143FAF for ; Tue, 8 Apr 2003 07:28:17 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0064.cvx40-bradley.dialup.earthlink.net ([216.244.42.64] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 192u55-0003Ba-00; Tue, 08 Apr 2003 07:28:12 -0700 Message-ID: <3E92DC28.6281F203@mindspring.com> Date: Tue, 08 Apr 2003 07:26:48 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alex.Wilkinson@dsto.defence.gov.au References: <20030407143118.V1049@squirm.dsto.defence.gov.au> <20030408161241.S70285@squirm.dsto.defence.gov.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40fe43f1e6b209be9ad654b963c1546d2a8438e0f32a48e08350badd9bab72f9c350badd9bab72f9c cc: current@freebsd.org cc: Dag-Erling Smorgrav Subject: Re: SCHED_ULE question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2003 14:28:18 -0000 "Wilkinson,Alex" wrote: > Cool, thanks for that, but what's the diff between: > > #sysctl kern.quantum > kern.quantum: 100000 > > AND > > #sysctl kern.quntum > sysctl: unknown oid 'kern.quntum' You mispelled it... but it's not there in SCHED_ULE. > What is meant to 'quantum' ? A quantum is the longest interval that a process is allowed to run in the presence of another ready-to-run process existing, without voluntarily releasing the CPU for another process to run (e.g. by making a blocking system call that doesn't result in a threads context switch to another thread in the same process). It is the granularity at which some schedulers implement time sharing. Use a search engine to search for the independent terms: scheduler quantum See also: lbolt -- Terry