From owner-freebsd-current Sun Sep 17 7:45:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 1A5D537B42C for ; Sun, 17 Sep 2000 07:45:19 -0700 (PDT) Received: (qmail 13751 invoked from network); 17 Sep 2000 14:45:14 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 17 Sep 2000 14:45:14 -0000 Date: Mon, 18 Sep 2000 01:45:10 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Alexander Leidinger Cc: current@FreeBSD.ORG, jhb@FreeBSD.ORG Subject: Re: 100% system time? (SMPng on UP system) In-Reply-To: <200009171427.e8HERFn34982@Magelan.Leidinger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Sep 2000, Alexander Leidinger wrote: > On 18 Sep, Bruce Evans wrote: > > >> >> dnetc runns with idprio 31, system cvsupped around Sep 16, 11 CEST from > >> >> a german mirror (it contains the idle fixes: src/sys/kern/kern_idle.c,v > >> >> 1.4), complete build{world,kernel}. > >> >> > >> >> ---snip--- > >> >> last pid: 1666; load averages: 1.10, 1.11, 1.03 up 0+00:51:21 16:54:14 > >> > > >> > Perhaps it really is a system process :-[. idprio on a pure cpu hog prevents > >> > other user processes from running like a system process might do: > >> > > >> > idprio 31 sh -c "while :; do :; done" > >> > > >> > System processes actually hang the entire system until they complete: > >> > >> Are you mixing idprio with rtprio or did I not understand what you > >> explain? > > > > You didn't understand :-). Try the example. It only uses idprio. > > I have dnetc still running with idprio 31 and it didn't hang the entire > system (I'm able to write this mail and compiling a port in the > background while dnetc is running). dnetc presumably blocks occasionally, giving other processes a chance to run. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message