From owner-freebsd-arch@FreeBSD.ORG Mon Jun 21 12:19:33 2010 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E04F51065672; Mon, 21 Jun 2010 12:19:33 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 769118FC18; Mon, 21 Jun 2010 12:19:33 +0000 (UTC) Received: by iwn7 with SMTP id 7so4226131iwn.13 for ; Mon, 21 Jun 2010 05:19:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=WT7dFiyzg9D79P7ndnyQDEkjt3MYz6MeTZFfs6YSnEQ=; b=Th04HaA08EM83EyXuTtF7SMqyYL+cRLB2ZqBwa/lwNJ/NjZWWwiscZb+T4DaSfwE3C qplyJ5Mo6+y0Ysb4KXnccy8TO4GcK0sLhDjeAsbjVmQV2gHGc0+JV8FRc8STUR1GJ0cz S+TWBbH4l2Tt3y1ROvpFL6eowleyk32SKfaoE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LcMJ+uoOcV8yPJ8xRArsspJZLk1gVovEssdwlJlNUmhUxyedRNOkzYZjTwxjn53nPJ 4Ef1Fjx7XsxCdLaRNTEBiWV+3MUhuTxlcd5EAI5JZo9TQJCSnyMh+WYMTI4Kyo1+8vzf j+dH2bAgMPaAz5Oy+FhehPX2iaBh593Apv8no= MIME-Version: 1.0 Received: by 10.231.211.208 with SMTP id gp16mr5252671ibb.133.1277122772597; Mon, 21 Jun 2010 05:19:32 -0700 (PDT) Received: by 10.231.182.212 with HTTP; Mon, 21 Jun 2010 05:19:32 -0700 (PDT) In-Reply-To: <4C1EF99B.5080300@FreeBSD.org> References: <4C0C1AE4.8050807@FreeBSD.org> <4C1DB296.5040605@FreeBSD.org> <4C1E381B.30405@FreeBSD.org> <4C1E7B89.1030005@FreeBSD.org> <4C1EF99B.5080300@FreeBSD.org> Date: Mon, 21 Jun 2010 07:19:32 -0500 Message-ID: From: Brandon Gooch To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-arch@freebsd.org, Doug Barton , FreeBSD-Current Subject: Re: RFC: New event timers infrastructure X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 12:19:34 -0000 On Mon, Jun 21, 2010 at 12:33 AM, Alexander Motin wrote: > Brandon Gooch wrote: >> On Sun, Jun 20, 2010 at 3:35 PM, Doug Barton wrote: >>> On 06/20/10 08:47, Alexander Motin wrote: >>>> While this can be done in sysctl.conf, it would be better to do it in >>>> loader.conf to make it applied from the beginning, without on-the-fly >>>> timers change. >>> You're probably right that for something this fundamental it's better to do >>> it in loader.conf, however I wanted to mention that I recently changed the >>> rcorder for the "early" boot scripts to run sysctl first for very similar >>> reasons. >> >> This is good information, so sorry if I'm being dense: does this mean >> that it should have worked by applying the changes via >> /etc/sysctl.conf? > > "You are too old. You are already born." (c) Sergey Lukyanenko. > stathz set much earlier, just before "Starting kernel event timers" > logged first time. It can only be affected from loader.conf. OK. I understand everything[*] now... >> No worries though, I've set it in /boot/loader.conf to avoid any >> possible ambiguity or anomalous behavior, and it's working very well! > > Nice. Very nice :) > BTW, I've successfully tested suspend/resume on my amd64 laptop with all > timers. For me, suspend/resume trials will be this evening, U.S. Central Standard Time... Looking forward to it! -Brandon [*] Well, almost everything, except for the Russian Sci-Fi quote ;)