From owner-freebsd-arch@FreeBSD.ORG Mon Jun 21 05:33:20 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 9926E106566B; Mon, 21 Jun 2010 05:33:20 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id C4E838FC18; Mon, 21 Jun 2010 05:33:19 +0000 (UTC) Received: by fxm7 with SMTP id 7so1990416fxm.13 for ; Sun, 20 Jun 2010 22:33:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=aODvdZ9To/0laQq0Li3kigSDHSR+CFm2OelmL3XwuVc=; b=u31L6I1AQgHprDWpHOVz8Ygy0tUdhVOBzBAYXWXgU8Cvc4sa5lvvD62jRun/rnavqX cnw8sc3o5Kr4t4xRSCm6FxylY23L8z6OHt/0Rkena3D6RQQ7l1Xpu6rxSBgoQKG1NWZ1 iu2Fc4+P/sIGp7VTpQpCrBVaUbCvzGjQjhAn4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=mBeeamvmvT86+c8ItsT4CkMsK7sKDjbc4opvTethZl2TfgFy99imQt4KgqvOTXYceZ bPFNATrH2BrWjXmTXFujHCzDBRXb8djQCts2+V8BxCAErAPB2MAhy8JnCNBV75brH19Q nJXAjDjF6gFOdIIPTdQzOks0jDKza8armxdeU= Received: by 10.223.18.154 with SMTP id w26mr4448079faa.39.1277098398782; Sun, 20 Jun 2010 22:33:18 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id y12sm32217440faj.5.2010.06.20.22.33.17 (version=SSLv3 cipher=RC4-MD5); Sun, 20 Jun 2010 22:33:18 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C1EF99B.5080300@FreeBSD.org> Date: Mon, 21 Jun 2010 08:33:15 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.24 (X11/20100402) MIME-Version: 1.0 To: Brandon Gooch References: <4C0C1AE4.8050807@FreeBSD.org> <4C1DB296.5040605@FreeBSD.org> <4C1E381B.30405@FreeBSD.org> <4C1E7B89.1030005@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 05:33:20 -0000 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. > 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. BTW, I've successfully tested suspend/resume on my amd64 laptop with all timers. -- Alexander Motin