From owner-freebsd-performance@FreeBSD.ORG Tue Apr 19 23:14:35 2011 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2073F106564A; Tue, 19 Apr 2011 23:14:35 +0000 (UTC) (envelope-from cowbert@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id BC64C8FC08; Tue, 19 Apr 2011 23:14:34 +0000 (UTC) Received: by vws18 with SMTP id 18so214608vws.13 for ; Tue, 19 Apr 2011 16:14:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=GqWcOPWzWxBY/8ORqi/u8yVXcRqCf7wdzYigkGnFTMQ=; b=ifZn2482U3qfJUrQX7Gkan9/6P5uk+QxkxEzrsmg5CYaZ6lPKlK2V6PvHL9uZWOddf rolRaT2nJfmqmR1yE2Y4WlMex5YXr2+UQqKbwSj6cbKNTUQpPCJ5rZ7v2scGpvcsrRPg 81rD0iIvGzP90HbrQMqc8ZBN1Tn1Z7N/9FyCk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=JJc25E+Qgb8TFfITrenWoFm52LYRvYewJGPz2mXWE1ViyIrDYZvK4VAOdtbm1BlcVq wkKhVt8zDN8bsysBYDnm31DTXCIQOHGomH2QIZvcdfdYCOPHb8jFTBmfqmL8Eaoh/cpG +k+sCYv4H1NjZwD7ne+ZAMRb9nu/dc1ksX0zk= MIME-Version: 1.0 Received: by 10.52.69.197 with SMTP id g5mr636837vdu.31.1303253012225; Tue, 19 Apr 2011 15:43:32 -0700 (PDT) Received: by 10.52.158.168 with HTTP; Tue, 19 Apr 2011 15:43:32 -0700 (PDT) Date: Tue, 19 Apr 2011 17:43:32 -0500 Message-ID: From: Peter Lai To: freebsd-stable@freebsd.org, freebsd-performance@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Tue, 19 Apr 2011 23:24:46 +0000 Cc: Subject: t_delta too short while trying to enable C3/TurboBoost X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2011 23:14:35 -0000 Hello I'm trying to enable C3 states to allow TurboBoost on RELENG_8_2 and dmesg is throwing a lot of t_delta too short messages while using boot -v. This platform is 2x Xeon E5620 Gulftown quad core 2.4ghz CPUs on whatever boards Dell ships them on these days (probably Intel X58 derivative.) Kernel is GENERIC for the most part (with network drivers stripped out). Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2394012372 Hz TSC: P-state invariant ACPI timer: 1/2 1/2 1/1 1/2 1/2 1/1 1/2 1/2 1/2 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 Here are my loader.conf: hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 kern.hz=100 hint.apic.0.clock=0 hint.atrtc.0.clock=0 rc.conf: performance_cpu_freq="NONE" # Online CPU frequency economy_cpu_freq="NONE" # Offline CPU frequency performance_cx_lowest="C3" # Online CPU idle state economy_cx_lowest="C3" # Offline CPU idle state and here is sysctl dev.cpu: dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU1 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.cx_supported: C1/1 C2/64 C3/96 dev.cpu.0.cx_lowest: C3 dev.cpu.0.cx_usage: 0.90% 0.45% 98.64% last 4096us dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU2 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.cx_supported: C1/1 C2/64 C3/96 dev.cpu.1.cx_lowest: C3 dev.cpu.1.cx_usage: 0.68% 0.34% 98.96% last 2965us dev.cpu.2.%desc: ACPI CPU dev.cpu.2.%driver: cpu dev.cpu.2.%location: handle=\_PR_.CPU3 dev.cpu.2.%pnpinfo: _HID=none _UID=0 dev.cpu.2.%parent: acpi0 dev.cpu.2.cx_supported: C1/1 C2/64 C3/96 dev.cpu.2.cx_lowest: C3 dev.cpu.2.cx_usage: 0.94% 0.66% 98.38% last 2081us dev.cpu.3.%desc: ACPI CPU dev.cpu.3.%driver: cpu dev.cpu.3.%location: handle=\_PR_.CPU4 dev.cpu.3.%pnpinfo: _HID=none _UID=0 dev.cpu.3.%parent: acpi0 dev.cpu.3.cx_supported: C1/1 C2/64 C3/96 dev.cpu.3.cx_lowest: C3 dev.cpu.3.cx_usage: 0.81% 0.58% 98.59% last 4124us dev.cpu.4.%desc: ACPI CPU dev.cpu.4.%driver: cpu dev.cpu.4.%location: handle=\_PR_.CPU5 dev.cpu.4.%pnpinfo: _HID=none _UID=0 dev.cpu.4.%parent: acpi0 dev.cpu.4.cx_supported: C1/1 C2/64 C3/96 dev.cpu.4.cx_lowest: C3 dev.cpu.4.cx_usage: 1.07% 0.68% 98.23% last 5046us dev.cpu.5.%desc: ACPI CPU dev.cpu.5.%driver: cpu dev.cpu.5.%location: handle=\_PR_.CPU6 dev.cpu.5.%pnpinfo: _HID=none _UID=0 dev.cpu.5.%parent: acpi0 dev.cpu.5.cx_supported: C1/1 C2/64 C3/96 dev.cpu.5.cx_lowest: C3 dev.cpu.5.cx_usage: 3.01% 1.74% 95.24% last 4504us dev.cpu.6.%desc: ACPI CPU dev.cpu.6.%driver: cpu dev.cpu.6.%location: handle=\_PR_.CPU7 dev.cpu.6.%pnpinfo: _HID=none _UID=0 dev.cpu.6.%parent: acpi0 dev.cpu.6.cx_supported: C1/1 C2/64 C3/96 dev.cpu.6.cx_lowest: C3 dev.cpu.6.cx_usage: 2.45% 1.89% 95.65% last 3506us dev.cpu.7.%desc: ACPI CPU dev.cpu.7.%driver: cpu dev.cpu.7.%location: handle=\_PR_.CPU8 dev.cpu.7.%pnpinfo: _HID=none _UID=0 dev.cpu.7.%parent: acpi0 dev.cpu.7.cx_supported: C1/1 C2/64 C3/96 dev.cpu.7.cx_lowest: C3 dev.cpu.7.cx_usage: 1.21% 0.77% 98.00% last 4180us Should I increment kern.hz until the t_delta too short goes away (I hear that at kern.hz=1000, each core is woken so much by the interrupt counter that it can never enter C3 state) or is there another knob I am supposed to tune? My goal is to see if I can get the box into turboboost as much as possible during idle. From owner-freebsd-performance@FreeBSD.ORG Wed Apr 20 10:40:59 2011 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2000D1065670 for ; Wed, 20 Apr 2011 10:40:59 +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 A23838FC17 for ; Wed, 20 Apr 2011 10:40:58 +0000 (UTC) Received: by fxm11 with SMTP id 11so481306fxm.13 for ; Wed, 20 Apr 2011 03:40:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature: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=iO2XZk0TfXugEQ4OspeHpNhabmKytu/5C/htj9W6sY4=; b=X59w1LOVsHmH3CzOSvUHbWFCWc6kul/9neWmPS79gh+ukE2byR8r1fNJHBMvMEuR3R yM71jFmuL+Ka5V3utNEmH/ea/BNt5b9cUjvRXVtC8mUiTYxNaZWf2fKVyLo9nJynv5cA saa7LnrtPMngHP+9rQvIy0y2mrLtO2AjTEOF0= 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=Xix1Fv0J9ZEgnzMCRFPFNGqMHGe+FudVGqMzxCqpl3OD10uc1vvf4T+PEqLpdCssjo Q+94qpPrQIMgtLixU4ofRJ+5z1c55HrlEU8zNwEsu3DbmWylWgFydw1CFK1q9UBmLGg9 38vtrql3Oe7wZo11TRlv2FhnFfrKIeHTWhILI= Received: by 10.223.6.11 with SMTP id 11mr94693fax.99.1303294707141; Wed, 20 Apr 2011 03:18:27 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id b18sm237936fak.32.2011.04.20.03.18.25 (version=SSLv3 cipher=OTHER); Wed, 20 Apr 2011 03:18:26 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DAEB2DF.60200@FreeBSD.org> Date: Wed, 20 Apr 2011 13:18:07 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Peter Lai References: In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 20 Apr 2011 11:02:05 +0000 Cc: freebsd-performance@freebsd.org Subject: Re: t_delta too short while trying to enable C3/TurboBoost X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2011 10:40:59 -0000 Peter Lai wrote: > I'm trying to enable C3 states to allow TurboBoost on RELENG_8_2 and > dmesg is throwing a lot of t_delta too short messages while using boot > -v. Most likely you can safely ignore these messages. They are probably result of the bug in checks that are not relevant any more. The bug periodically triggered with some probability if HZ set lower then some level. These checks were removed in 9-CURRENT. -- Alexander Motin