From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eg@gaute.vetsj.com>
Received: from localhost (c1367BF51.dhcp.bluecom.no [81.191.103.19])
        by mx.google.com with ESMTPS id x54sm835523eeh.17.2010.11.10.08.13.32
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Wed, 10 Nov 2010 08:13:34 -0800 (PST)
Content-Type: text/plain; charset=UTF-8
From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] really high wakeup count in powertop
In-reply-to: <1289399902-sup-201@think>
References: <1289349454-sup-1015@think> <1289399902-sup-201@think>
Date: Wed, 10 Nov 2010 17:13:48 +0100
Message-Id: <1289405570-sup-2035@qwerzila>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

Excerpts from Chris Mason's message of 2010-11-10 15:41:30 +0100:
> strace showed we were hammering on futexes, and a little digging made it
> clear sup isn't to blame.  The ruby timer thread is polling for
> signals (or something) every 10ms:
> 
> http://redmine.ruby-lang.org/issues/show/3436
> 
> I patched up ruby to poll every 500ms and things seem to work.  Not sure
> why the ruby developers didn't just change the timeout, but chances are
> good they have a real reason.  I'll post to that bug.

Also noticed sup in powertop; so there's nothing to do on the Sup side ?

- gaute