From owner-freebsd-current@FreeBSD.ORG Tue Nov 5 18:13:06 2013 Return-Path: Delivered-To: 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 ESMTP id C9A5876B; Tue, 5 Nov 2013 18:13:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 528222B49; Tue, 5 Nov 2013 18:13:06 +0000 (UTC) Received: by mail-qa0-f50.google.com with SMTP id f11so1237080qae.2 for ; Tue, 05 Nov 2013 10:13:05 -0800 (PST) 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=ZPOoisM4obD39jBxv1JSlAUS7nKz7ByCr6Z6jdrYuZo=; b=Mbgz33ETp7juUka/XgpR5Sd0FjST6Pr9WghQefhEem9P/c2aJmLpYiQ6M+LAFOFWzU K+Oh8vlfoc0jX8mqdGH0aSZ/qhq9xzuMd0NqNzME0lQ2b4hLZyrHxWJ2zOCDkCu0PpqY LKnH7ZVSUhwtE05diRTbMNNwMk8IGyOFj8PaT8YWk5yAtXDk8lE1WHML2qrhewIZhdlm gYwdCW1GKsofbv04/MuzsNcPD/0qTC2YX7/Sa04ad9GyMr+UMfYpzutKNGC/QCLx9qWp ELKUFZDQPnucWZgWw92ClCZq+gQMMxEyjZUjtKorLFe+pfUSO5LHUVlFA+wu7TSOHRDE cEWQ== MIME-Version: 1.0 X-Received: by 10.229.244.69 with SMTP id lp5mr31174429qcb.14.1383675185144; Tue, 05 Nov 2013 10:13:05 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 5 Nov 2013 10:13:05 -0800 (PST) In-Reply-To: References: Date: Tue, 5 Nov 2013 10:13:05 -0800 X-Google-Sender-Auth: o1IbbFiUBcDEZVVqprDpYgvU3p0 Message-ID: Subject: Re: [10-STABLE, 11-CURRENT] something wrong between cam and eventtimer or geom and eventtimer From: Adrian Chadd To: Oliver Pinter Content-Type: text/plain; charset=ISO-8859-1 Cc: Davide Italiano , Alexander Motin , FreeBSD Stable Mailing List , "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Tue, 05 Nov 2013 18:13:06 -0000 and sysctl machdep.idle_mwait=0 -adrian On 5 November 2013 10:12, Adrian Chadd wrote: > Ok, so it's only hitting C1. It's not going into C2. > > Is this a dual core CPU with hyperthreading enabled, or a quad core CPU? > > How about changing the idle loop from acpi to hlt, see if that fixes > things? (Without tweaking the event timer logic.) > > I'm worried that what you're seeing here are missed interrupts or > interrupts that aren't immediately causing the driver thread to be > scheduled (and thus things enter HLT until the next interrupt.) I had > to deal with this crap on MIPS for quite some time. > > sysctl machdep.idle=hlt > > > > -adrian > > > On 5 November 2013 09:25, Oliver Pinter wrote: >> op@perpetua ~> sysctl dev.cpu >> 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.coretemp.delta: 59 >> dev.cpu.0.coretemp.resolution: 1 >> dev.cpu.0.coretemp.tjmax: 100.0C >> dev.cpu.0.coretemp.throttle_log: 0 >> dev.cpu.0.temperature: 41.0C >> dev.cpu.0.freq_levels: 3401/84000 3400/84000 3200/77169 3000/70587 >> 2800/64262 2700/61182 2500/55201 2300/49464 2100/43946 1900/38654 >> 1700/34277 1500/29407 1400/27053 1225/23671 1200/22509 1050/19695 >> 1000/18167 875/15896 800/14031 700/12277 600/10523 500/8769 400/7015 >> 300/5261 200/3507 100/1753 >> dev.cpu.0.cx_supported: C1/1/1 C2/2/67 >> dev.cpu.0.cx_lowest: C1 >> dev.cpu.0.cx_usage: 100.00% 0.00% last 812us >> 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.coretemp.delta: 56 >> dev.cpu.1.coretemp.resolution: 1 >> dev.cpu.1.coretemp.tjmax: 100.0C >> dev.cpu.1.coretemp.throttle_log: 0 >> dev.cpu.1.temperature: 44.0C >> dev.cpu.1.cx_supported: C1/1/1 C2/2/67 >> dev.cpu.1.cx_lowest: C1 >> dev.cpu.1.cx_usage: 100.00% 0.00% last 1348us >> 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.coretemp.delta: 61 >> dev.cpu.2.coretemp.resolution: 1 >> dev.cpu.2.coretemp.tjmax: 100.0C >> dev.cpu.2.coretemp.throttle_log: 0 >> dev.cpu.2.temperature: 39.0C >> dev.cpu.2.cx_supported: C1/1/1 C2/2/67 >> dev.cpu.2.cx_lowest: C1 >> dev.cpu.2.cx_usage: 100.00% 0.00% last 845us >> 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.coretemp.delta: 62 >> dev.cpu.3.coretemp.resolution: 1 >> dev.cpu.3.coretemp.tjmax: 100.0C >> dev.cpu.3.coretemp.throttle_log: 0 >> dev.cpu.3.temperature: 38.0C >> dev.cpu.3.cx_supported: C1/1/1 C2/2/67 >> dev.cpu.3.cx_lowest: C1 >> dev.cpu.3.cx_usage: 100.00% 0.00% last 1609us >> >> On 11/5/13, Adrian Chadd wrote: >>> Hi! >>> >>> Can you do 'sysctl dev.cpu' please? I'd like to see what sleep >>> state(s) your CPU is entering. >>> >>> Thanks! >>> >>> >>> -adrian >>> >>> >>> On 5 November 2013 06:07, Oliver Pinter wrote: >>>> Hi all! >>>> >>>> The machine is a Haswell machine, the disc performance was very poor >>>> (20-30MByte/sec). >>>> When I change the kern.eventtimer.idletick from 0 to 1, the normal >>>> performance restored back to normal (70-90MByte/sec). >>>> >>>> The default eventtimer was LAPIC. >>>> >>>> On other machine Q9300, this was fully reproducible. >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to >>>> "freebsd-current-unsubscribe@freebsd.org" >>>