From owner-freebsd-current@FreeBSD.ORG Mon May 12 18:25:43 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D374CB7E for ; Mon, 12 May 2014 18:25:43 +0000 (UTC) Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 93C9521A6 for ; Mon, 12 May 2014 18:25:43 +0000 (UTC) Received: by mail-qg0-f50.google.com with SMTP id z60so8199086qgd.9 for ; Mon, 12 May 2014 11:25:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=DMvyKGfLFfMgIq1LylfGlP/zPh0IwyrEnA08LBZkYMQ=; b=N4tJ/XwFPxIpIag/RN2QIIsOFb7J3h+L98KOEhGhgo13p0vJ/LiblTCkO61zkkceeK cQRBScMboh/cIyrZudr6DR1nOGD8zO3P6VJSK9JorhkkN0SGb9n+v4h+9qO6XxgriUVc 7fNe1JubOL5nNLymRublNyLodGEiDn8g3SSpIV2roNzKjdv4D5q+UUE8iuBfwYtKXbDn Zct9ZLlgcKYsovck26WNSLiUO35M25ZEvhTObf4360Tv1AbMlvGrn/gmylL6NOZ4n7d6 MjFJYyMksEea8H7c40BL+MjK1hRE2Ui2T+VptsOtmuNDjh3ewiTMQwL47YjVwAfu+QbW AUvQ== MIME-Version: 1.0 X-Received: by 10.140.22.209 with SMTP id 75mr39066026qgn.4.1399919142616; Mon, 12 May 2014 11:25:42 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Mon, 12 May 2014 11:25:42 -0700 (PDT) In-Reply-To: <53710656.6030303@allanjude.com> References: <20140506163823.GA1406@tiny-r255948> <53710656.6030303@allanjude.com> Date: Mon, 12 May 2014 11:25:42 -0700 X-Google-Sender-Auth: 01CdEck46W6xexd2N7Z57wytXRE Message-ID: Subject: Re: Leaving the Desktop Market From: Adrian Chadd To: Allan Jude Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2014 18:25:44 -0000 On 12 May 2014 10:35, Allan Jude wrote: > I have this system: > > hw.model: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz > hw.ncpu: 4 > > http://ark.intel.com/products/75052 > > dev.cpu.0.%desc: ACPI CPU > dev.cpu.0.%driver: cpu > dev.cpu.0.%location: handle=\_PR_.CPU0 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%parent: acpi0 > dev.cpu.0.freq: 3100 > dev.cpu.0.freq_levels: 3101/80000 3100/80000 2900/72713 2800/69558 > 2600/62669 2400/56794 2300/53935 2100/47673 1900/42370 1800/39795 > 1600/34136 1500/31729 1300/26432 1137/23128 1100/21994 1000/19851 > 875/17369 800/15113 700/13223 600/11334 500/9445 400/7556 300/5667 > 200/3778 100/1889 > dev.cpu.0.cx_supported: C1/1/1 C2/2/148 > dev.cpu.0.cx_lowest: C8 > dev.cpu.0.cx_usage: 9.01% 90.98% last 807us > dev.cpu.1.%desc: ACPI CPU > dev.cpu.1.%driver: cpu > dev.cpu.1.%location: handle=\_PR_.CPU1 > dev.cpu.1.%pnpinfo: _HID=none _UID=0 > dev.cpu.1.%parent: acpi0 > dev.cpu.1.cx_supported: C1/1/1 C2/2/148 > dev.cpu.1.cx_lowest: C8 > dev.cpu.1.cx_usage: 11.70% 88.29% last 21303us > dev.cpu.2.%desc: ACPI CPU > dev.cpu.2.%driver: cpu > dev.cpu.2.%location: handle=\_PR_.CPU2 > dev.cpu.2.%pnpinfo: _HID=none _UID=0 > dev.cpu.2.%parent: acpi0 > dev.cpu.2.cx_supported: C1/1/1 C2/2/148 > dev.cpu.2.cx_lowest: C8 > dev.cpu.2.cx_usage: 15.17% 84.82% last 22987us > dev.cpu.3.%desc: ACPI CPU > dev.cpu.3.%driver: cpu > dev.cpu.3.%location: handle=\_PR_.CPU3 > dev.cpu.3.%pnpinfo: _HID=none _UID=0 > dev.cpu.3.%parent: acpi0 > dev.cpu.3.cx_supported: C1/1/1 C2/2/148 > dev.cpu.3.cx_lowest: C8 > dev.cpu.3.cx_usage: 11.74% 88.25% last 6073us > So ACPI is exposing C1 and C2 only. > According to the Intel specs (Page 11), this processor supports C1, C1E, > C3, C6 and C7 > > The above sysctl dump shows only C1 and C2. I wonder if the C2 is > actually C3 > > http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/xeon-e3-1200v3-vol-1-datasheet.pdf It'd say C2/3/xxx in that case. Chances are you'll end up seeing it fall into deeper sleep states. Try installing intel-pcm; kldload cpuctl; run pcm.x 1 . See if it's entering lower CPU states. > How is our support for the newer Cx States introduced in Haswell, which > can apparently go as high as C10 I don't know if we get those exposed via ACPI. I know there's a bunch of cute things we could be doing with MWAIT that we aren't, but we certainly should be drifting into lower sleep states. Just run intel-pcm and see. Thanks, -a