Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754582AbbGCCe3 (ORCPT ); Thu, 2 Jul 2015 22:34:29 -0400 Received: from mga11.intel.com ([192.55.52.93]:8520 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754521AbbGCCeX (ORCPT ); Thu, 2 Jul 2015 22:34:23 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,396,1432623600"; d="scan'208";a="757651495" Date: Fri, 3 Jul 2015 02:42:34 +0800 From: Yuyang Du To: Morten Rasmussen Cc: Peter Zijlstra , Rabin Vincent , Mike Galbraith , "mingo@redhat.com" , "linux-kernel@vger.kernel.org" , Paul Turner , Ben Segall Subject: Re: [PATCH?] Livelock in pick_next_task_fair() / idle_balance() Message-ID: <20150702184234.GC5197@intel.com> References: <20150630143057.GA31689@axis.com> <1435728995.9397.7.camel@gmail.com> <20150701145551.GA15690@axis.com> <20150701204404.GH25159@twins.programming.kicks-ass.net> <20150701232511.GA5197@intel.com> <20150702105359.GY19282@twins.programming.kicks-ass.net> <20150702114454.GB7598@e105550-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150702114454.GB7598@e105550-lin.cambridge.arm.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1971 Lines: 44 On Thu, Jul 02, 2015 at 12:44:55PM +0100, Morten Rasmussen wrote: > On Thu, Jul 02, 2015 at 12:53:59PM +0200, Peter Zijlstra wrote: > > On Thu, Jul 02, 2015 at 07:25:11AM +0800, Yuyang Du wrote: > > > And obviously, the idle balancing livelock SHOULD happen: one CPU pulls > > > tasks from the other, makes the other idle, and this iterates... > > > > > > That being said, it is also obvious to prevent the livelock from happening: > > > idle pulling until the source rq's nr_running is 1, becuase otherwise we > > > just avoid idleness by making another idleness. > > > > Well, ideally the imbalance calculation would be so that it would avoid > > this from happening in the first place. Its a 'balance' operation, not a > > 'steal everything'. > > > > We want to take work -- as we have none -- but we want to ensure that > > afterwards we have equal work, ie we're balanced. > > Agreed, I think this is the true problem. See my other reply. Yes, this is agreed at all time. Like I said load_balance() (for idle balancing) should compute the right imbalance and move a fair amount, to achieve we are balanced. Whatever is wrong in how much computed and moved "right imbalance" is should be fixed anyway. But still, I think, even with the above, in idle balancing, pulling until the source rq's nr_running == 1 is not just "a short term fix", but should be there permanently acting like a last guard with no overhead, why not. > > > > > So clearly that all is hosed. Now Morten was looking into simplifying > > calculate_imbalance() recently. > > Yes. I'm held up doing other stuff at the moment, but I think > calculate_imbalance() needs some attention and I'm planning on looking at > that next. Thanks, Yuyang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/