From owner-freebsd-ppc@FreeBSD.ORG Thu Jul 25 20:37:23 2013 Return-Path: Delivered-To: freebsd-ppc@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 59DDAA97; Thu, 25 Jul 2013 20:37:23 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 072AE2EED; Thu, 25 Jul 2013 20:37:22 +0000 (UTC) Received: by mail-oa0-f49.google.com with SMTP id n12so5513166oag.36 for ; Thu, 25 Jul 2013 13:37:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=GVKW2uqi4jjMHno3l5dHxzWLhhN5fQR6HD51M/2JFSM=; b=j8zl/ppDO53vdMLGaTyL34gYpQQ4I/A85gX4VT7p+9sILqPPThoIGKiamgQirQMwN8 5fttjop381Jod0LlSTQf/202oCAyvAAnnhtJn1G7HTaaROrhoGwE4HJO9Ke4BeKgk6CL PCaMDh1dGUpQcjHySoiqe2nZ1MxI9jsbf9FqbgqME2EVA5BdH081YcQlDCwKrnICx2uG Y0aYy6183wKKzlxyV1MIo+n8ZV9MtQjxUWZTb9YbOkMivP3gxal1xe3nCNbGuLz+8D2t BIa7lU0dwe3P7uxD4h2VDNBGnl9hr5WN8Gg9vHtFtYFpdEK/X5PI/O7pJUXJB4eJlZSu ErVg== MIME-Version: 1.0 X-Received: by 10.60.102.41 with SMTP id fl9mr44534074oeb.37.1374784642376; Thu, 25 Jul 2013 13:37:22 -0700 (PDT) Received: by 10.182.115.194 with HTTP; Thu, 25 Jul 2013 13:37:22 -0700 (PDT) In-Reply-To: References: Date: Thu, 25 Jul 2013 16:37:22 -0400 Message-ID: Subject: Re: Kern.hz= +1 hertz at anything 2500 and above. From: Super Bisquit To: Adrian Chadd , FreeBSD PowerPC ML , freebsd-current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jul 2013 20:37:23 -0000 On Thu, Jul 25, 2013 at 12:11 PM, Adrian Chadd wrote: > On 25 July 2013 02:51, Wojciech Puchar > wrote: > >> improved with a higher kern.hz rating. Unless the future holds an > emu20k2, > >> there will be RAM used from the motherboard. > >> 1. I will need a real-time or a faster kernel- hence the high rate > wanted- > >> because the devices to be built will be used in an active environment: > >> art, > >> music, audio control. > >> 2. Any system with limited memory and a low CPU hertz rate benefits from > >> the higher kern.hz setting. > > > rather opposite. more kern.hz=more interrupts. > > Right. > > More hz == more interrupts and less ability for a CPU-bound process to > chew all the CPU. > > So is it a scheduling issue, where you have multiple CPU bound > userland processes that aren't being fair and consuming all the CPU? > Is it that your device driver(s) aren't interrupting correctly, > relying on the hz tick to make up the slack, etc. > The G3 had the other scheduler- not ULE- when I built the system. > > Is it a busted halt loop, which is being papered over with hz ticks? > I wouldn't know. How would I test for this? > > Have you tried -10 on that kit, with the more aggressive clock/timer > code that won't interrupt unless it needs to? Set the rate to -10 ? I'll try the aggressive clock/timer code if someone would point me to a tutorial for setting it up. That sounds more like a solution I like. > Has that changed things? > If I can implement it, it may be the best solution. > > > > -adrian >