All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Fisher <bug-track@fisher-privat.net>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"power@bughost.org" <power@bughost.org>
Subject: Re: less load less performance
Date: Mon, 01 Nov 2010 09:50:39 +0100	[thread overview]
Message-ID: <1288601439.2632.17.camel@mini> (raw)
In-Reply-To: <4CCDE8AC.2060403@linux.intel.com>

Am Sonntag, den 31.10.2010, 15:07 -0700 schrieb Arjan van de Ven:
> On 10/31/2010 9:44 AM, Alexey Fisher wrote:
> > Hallo all,
> >
> > after testing latest intel_drm_next v2.6.36-07547-g100519e on my netbook
> > i have seen interesting issue. Standardly started glxgears performs not
> > so well, it drops some times to 25fps.
> > if start glxgears in fullscrean mode it performs well - about 60fps.
> 
> 
> funny that you mention this; I was just talking to Eric earlier about 
> this topic in a cab to the conference...
> ... we have some ideas on how to fix this.

It will be great to see some patches :D
i did some more powertop debuging to see what is the difference between
smp and non smp system.
Here are two dumps, i tried to do it more or less clean: "sleep 10;
powertop --dump" 

dump with maxcpus=1:
==========================================================
Cn	           Verweildauer
C0 (Prozessor läuft)    (33,0%)
zyklisches AbfraC1 mwait	  0,0ms ( 0,0%)
C1 mwait	  0,2ms ( 0,1%)
C2 mwait	  1,4ms ( 1,8%)
C4 mwait	  5,6ms (65,2%)
P-States (Frequenzen)
  1,67 GHz    23,8%
  1333 MHz     0,1%
  1000 MHz    76,1%
Aufwachen pro Sekunde : 132,2	Intervall: 15,0s
Stromverbrauch (ACPI-Schätzung): 10,2W (6,1 Std.) 
Häufigste Ursachen für das Aufwachen:
  34,1% ( 88,7)   [kernel scheduler] Load balancing tick
  23,1% ( 60,1)   [i915, uhci_hcd:usb5] <interrupt>
  12,1% ( 31,4)   firefox-bin
   9,2% ( 23,9)   [ath9k] <interrupt>
   4,7% ( 12,1)   evince


dump with smp/ht enabled:
===============================================
Ihre CPU unterstützt folgende C-Status: C1 C2 C4 
Ihr BIOS meldet folgende C-Status: C1 C2 C4 
Cn	           Verweildauer
C0 (Prozessor läuft)    (13,4%)
zyklisches AbfraC1 mwait	  0,0ms ( 0,0%)
C1 mwait	  2,2ms ( 2,6%)
C2 mwait	  3,6ms (41,8%)
C4 mwait	  1,5ms (42,3%)
P-States (Frequenzen)
  1,67 GHz    11,3%
  1333 MHz     0,1%
  1000 MHz    88,6%
Aufwachen pro Sekunde : 411,0	Intervall: 15,0s
Stromverbrauch (ACPI-Schätzung): 9,2W (6,5 Std.) 
Häufigste Ursachen für das Aufwachen:
  19,3% ( 50,0)   kworker/0:0
  17,9% ( 46,3)   [i915, uhci_hcd:usb5] <interrupt>
  15,6% ( 40,3)   [kernel scheduler] Load balancing tick
  13,3% ( 34,4)   PS/2 keyboard/mouse/touchpad interrupt
   8,3% ( 21,4)   [ath9k] <interrupt>
   4,7% ( 12,1)   evince
   4,0% ( 10,5)   [kernel core] hrtimer_start (tick_sched_timer)
========================================================================

With SMP it use less C0 and more C2,C4; with NONSMP it use mostly C0 and
C4 but is use _more_ power ...


If i start normal kernel also SMP but set one core offline after boot i
get this:
==========================================================================
Ihre CPU unterstützt folgende C-Status: C1 C2 C4 
Ihr BIOS meldet folgende C-Status: C1 C2 C4 
Cn	           Verweildauer
C0 (Prozessor läuft)    (39,8%)
zyklisches AbfraC1 mwait	  0,0ms ( 0,0%)
C1 mwait	  4,9ms ( 8,0%)
C2 mwait	 11,4ms (51,0%)
C4 mwait	  0,1ms ( 1,3%)
P-States (Frequenzen)
  1,67 GHz    34,0%
  1333 MHz     0,4%
  1000 MHz    65,6%
Aufwachen pro Sekunde : 301,1	Intervall: 15,0s
Stromverbrauch (ACPI-Schätzung): 9,7W (5,8 Std.) 
Häufigste Ursachen für das Aufwachen:
  39,1% ( 92,6)   [kernel scheduler] Load balancing tick
  22,6% ( 53,5)   [i915, uhci_hcd:usb5] <interrupt>
   5,7% ( 13,6)   [ahci] <interrupt>
   5,1% ( 12,1)   evince
   4,8% ( 11,3)   glxgears
   4,2% (  9,9)   desktopcouch-se


C4 is almost not used, but i still get bad performance. 

Do PM behave differently if i start with one Core and if i desable one
core after start?

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2010-11-01  8:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 16:44 less load less performance Alexey Fisher
2010-10-31 17:01 ` Peter Clifton
2010-10-31 17:40   ` Alexey Fisher
2010-10-31 19:18     ` [Intel-gfx] " Andreas Mohr
2010-10-31 19:44       ` Alexey Fisher
2010-11-02 15:53         ` [Intel-gfx] " Thomas Renninger
2010-10-31 17:33 ` Vasily Khoruzhick
2010-10-31 22:07 ` Arjan van de Ven
2010-11-01  8:50   ` Alexey Fisher [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1288601439.2632.17.camel@mini \
    --to=bug-track@fisher-privat.net \
    --cc=arjan@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=power@bughost.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.