From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.180.131 with SMTP id bu3cs80112icb; Wed, 10 Nov 2010 12:15:00 -0800 (PST) Received: by 10.42.221.198 with SMTP id id6mr560431icb.280.1289420099830; Wed, 10 Nov 2010 12:14:59 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id x21si3093412ibf.19.2010.11.10.12.14.59; Wed, 10 Nov 2010 12:14:59 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 92D70185837E for ; Wed, 10 Nov 2010 15:14:59 -0500 (EST) X-Greylist: delayed 3433 seconds by postgrey-1.31 at rubyforge.org; Wed, 10 Nov 2010 14:32:56 EST Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 1542E1858367 for ; Wed, 10 Nov 2010 14:32:55 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1PGFWI-0004OP-4o for sup-devel@rubyforge.org; Wed, 10 Nov 2010 13:35:42 -0500 From: William Morgan To: sup-devel In-reply-to: <1289399902-sup-201@think> References: <1289349454-sup-1015@think> <1289399902-sup-201@think> Date: Wed, 10 Nov 2010 13:35:41 -0500 Message-Id: <1289414078-sup-6701@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-devel] really high wakeup count in powertop X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Reformatted excerpts from Chris Mason's message of 2010-11-10: > 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. Yeah, the last time someone investigated this, they decided it was a Ruby issue as well. Keep us informed if that patch gets applied. You could also try 1.9.2 for kicks. -- William _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel