Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752731AbaKDIod (ORCPT ); Tue, 4 Nov 2014 03:44:33 -0500 Received: from mga03.intel.com ([134.134.136.65]:3077 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751247AbaKDIo3 (ORCPT ); Tue, 4 Nov 2014 03:44:29 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,312,1413270000"; d="scan'208";a="601829912" Date: Tue, 4 Nov 2014 16:23:45 +0800 From: Wanpeng Li To: Peter Zijlstra Cc: Ingo Molnar , Kirill Tkhai , Juri Lelli , linux-kernel@vger.kernel.org Subject: Re: [PATCH RFC] sched/deadline: support dl task migrate during cpu hotplug Message-ID: <20141104082345.GA22062@kernel> Reply-To: Wanpeng Li References: <1414740497-7232-1-git-send-email-wanpeng.li@linux.intel.com> <20141103104111.GA23531@worktop.programming.kicks-ass.net> <20141103235747.GA26702@kernel> <20141104083225.GG10501@worktop.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141104083225.GG10501@worktop.programming.kicks-ass.net> 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 Hi Peter, On Tue, Nov 04, 2014 at 09:32:25AM +0100, Peter Zijlstra wrote: >On Tue, Nov 04, 2014 at 07:57:48AM +0800, Wanpeng Li wrote: >> On Mon, Nov 03, 2014 at 11:41:11AM +0100, Peter Zijlstra wrote: > >> >On Fri, Oct 31, 2014 at 03:28:17PM +0800, Wanpeng Li wrote: >> >So what is wrong with making dl_task_timer() deal with it? The timer >> >will still fire on the correct time, canceling it and or otherwise >> >messing with the CBS is wrong. Once it fires, all we need to do is >> >migrate it to another cpu (preferably one that is still online of course >> >:-). > >> Do you mean what I need to do is push the task to another cpu in dl_task_timer() >> if rq is offline? > >That does indeed appear to be the sensible fix to me. > >> In addition, what will happen if dl task can't preempt on >> another cpu? > >So if we find that the rq the task was on is no longer available, we >need to select a new rq, the 'right' rq would be the one running the >latest deadline. > >If it cannot preempt the latest (running) deadline, it was not eligible >for running in the first place so no worries, right? I think this will lead to this deadline task cannot running on any rqs any more. If my understanding is not right, when it will be picked? Regards, Wanpeng Li -- 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/