From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 08:32:24 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 04703885 for ; Wed, 7 Aug 2013 08:32:24 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E28642562; Wed, 7 Aug 2013 08:32:23 +0000 (UTC) Received: from xyf.my.dom (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r778WMsp022143; Wed, 7 Aug 2013 08:32:23 GMT (envelope-from davidxu@freebsd.org) Message-ID: <5202063F.9070706@freebsd.org> Date: Wed, 07 Aug 2013 16:33:03 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130416 Thunderbird/17.0.5 MIME-Version: 1.0 To: dave@mischler.com Subject: Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1 References: <1375737316.96778.10.camel@firkin.mischler.com> In-Reply-To: <1375737316.96778.10.camel@firkin.mischler.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 08:32:24 -0000 On 2013/08/06 05:15, Dave Mischler wrote: > I have an i5-2500 machine 8GB RAM now running 9.2-RC1 amd64 with the > GENERIC kernel. Today, while still running 9.2-BETA2, I updated my > source tree and started building world with idprio 31 and I looked back > a while later and all the CPU cores and disk were essentially idle, and > hardly any progress had been made on the build. I stopped and restarted > the build without the idle priority setting and it ran fine. Anybody > else seen any of this? Anybody know about any fairly recent changes that > might account for it? > > I did a "rm -rf /usr/src /usr/obj" and loaded a new source tree before > going to RC1. I still see odd behavior at RC1. Sometimes it works just > like it should (i.e. compute bound processes use most/all of the > available CPU time), but a lot of the time both the CPU and disk are > idle (e.g. CPU 97.8% idle, disk 1% busy per systat). I don't think I > ever saw this behavior before while running "make buildworld -j4". Can > anyone else confirm/rebut my findings? Thanks. > > idle should never be used, it can cause long term priority inversion in kernel, make the system slower.