From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752821AbbERIch (ORCPT ); Mon, 18 May 2015 04:32:37 -0400 Received: from casper.infradead.org ([85.118.1.10]:43975 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751966AbbERIcg (ORCPT ); Mon, 18 May 2015 04:32:36 -0400 Date: Mon, 18 May 2015 10:32:16 +0200 From: Peter Zijlstra To: pang.xunlei@zte.com.cn Cc: dedekind1@gmail.com, juri.lelli@arm.com, linux-kernel@vger.kernel.org, linux-kernel-owner@vger.kernel.org, mgorman@suse.de, mingo@kernel.org, riel@redhat.com, rostedt@goodmis.org Subject: Re: [RFC][PATCH 3/4] sched: Change sched_class::set_cpus_allowed calling context Message-ID: <20150518083216.GB21418@twins.programming.kicks-ass.net> References: <20150515154333.712161952@infradead.org> <20150515154833.667516139@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 18, 2015 at 03:37:43PM +0800, pang.xunlei@zte.com.cn wrote: > Hi Peter, > > With this modification, I think the pushing action in my previous patch > "Check to push the task away after its affinity was changed" will not > be able to be implemented inside sched_class::set_cpus_allowed(). Ah, right, I knew there was a patch I needed to look at. I'll try and not forget, but there's a few regression reports I need to look at first.